The Bad-Attitude Guide to Computer Security
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Reducing the Window of Exposure
Surviving 0-days reducing the window of exposure Andreas Lindh, VB2013 About me • Security analyst/architect • Used to work for Volvo IT • Defender by profession • @addelindh on Twitter So what’s this about? • Software vulnerabilities, exploits and the current defense model • A suggested way of improving that model Defense Legacy implementation • Perimeter protection • Access controls • System hardening • Antivirus Evolution • All the legacy and more: – SIEM – DLP – Application firewalls – Etc. • Basically, more tools Client-side attacks Got protection? What does this mean? • The perimeter changed • Our defenses didn’t • Antivirus to the rescue? The New York Times hack So how did we get here? • Human nature – Easier to buy tools than to work hard – Bad prioritization • Defense isn't sexy "Put another way, n people want to fix security holes, 10n people want to exploit security holes, and 100000n want Tetris.” (Dan Kaminsky) But we patch, right? Well, sort of but... • We do it slowly • Sometimes we can’t patch – Legacy systems – 3rd party systems HD Moore’s law What about 0-days? The Microsoft report This can’t be good... • 46% of Remote Code Execution vulnerabilities exploited before patch available in 2012 Source: Software Vulnerability Exploitation Trends ...and remember this? • Dec 2012 – Jan 2013 • The watering hole attack Wait a minute, wasn’t this supposed to be a talk about flashy 0-day defense? There is no flashy fix. Priorities, priorities Back to basics • Get re-acquainted with our environments • Start using the tools we already have • Focus on what matters Hardening • Usually only done high level • Not that effective anymore • Why don’t we do it to software? Learning from history • Where? • What? • Exploitability? • Protection? Software hardening • Exploit mitigation – ASLR, DEP, EMET, etc. -
The Double Ratchet Algorithm
The Double Ratchet Algorithm Trevor Perrin (editor) Moxie Marlinspike Revision 1, 2016-11-20 Contents 1. Introduction 3 2. Overview 3 2.1. KDF chains . 3 2.2. Symmetric-key ratchet . 5 2.3. Diffie-Hellman ratchet . 6 2.4. Double Ratchet . 13 2.6. Out-of-order messages . 17 3. Double Ratchet 18 3.1. External functions . 18 3.2. State variables . 19 3.3. Initialization . 19 3.4. Encrypting messages . 20 3.5. Decrypting messages . 20 4. Double Ratchet with header encryption 22 4.1. Overview . 22 4.2. External functions . 26 4.3. State variables . 26 4.4. Initialization . 26 4.5. Encrypting messages . 27 4.6. Decrypting messages . 28 5. Implementation considerations 29 5.1. Integration with X3DH . 29 5.2. Recommended cryptographic algorithms . 30 6. Security considerations 31 6.1. Secure deletion . 31 6.2. Recovery from compromise . 31 6.3. Cryptanalysis and ratchet public keys . 31 1 6.4. Deletion of skipped message keys . 32 6.5. Deferring new ratchet key generation . 32 6.6. Truncating authentication tags . 32 6.7. Implementation fingerprinting . 32 7. IPR 33 8. Acknowledgements 33 9. References 33 2 1. Introduction The Double Ratchet algorithm is used by two parties to exchange encrypted messages based on a shared secret key. Typically the parties will use some key agreement protocol (such as X3DH [1]) to agree on the shared secret key. Following this, the parties will use the Double Ratchet to send and receive encrypted messages. The parties derive new keys for every Double Ratchet message so that earlier keys cannot be calculated from later ones. -
Security Analysis of the Signal Protocol Student: Bc
ASSIGNMENT OF MASTER’S THESIS Title: Security Analysis of the Signal Protocol Student: Bc. Jan Rubín Supervisor: Ing. Josef Kokeš Study Programme: Informatics Study Branch: Computer Security Department: Department of Computer Systems Validity: Until the end of summer semester 2018/19 Instructions 1) Research the current instant messaging protocols, describe their properties, with a particular focus on security. 2) Describe the Signal protocol in detail, its usage, structure, and functionality. 3) Select parts of the protocol with a potential for security vulnerabilities. 4) Analyze these parts, particularly the adherence of their code to their documentation. 5) Discuss your findings. Formulate recommendations for the users. References Will be provided by the supervisor. prof. Ing. Róbert Lórencz, CSc. doc. RNDr. Ing. Marcel Jiřina, Ph.D. Head of Department Dean Prague January 27, 2018 Czech Technical University in Prague Faculty of Information Technology Department of Computer Systems Master’s thesis Security Analysis of the Signal Protocol Bc. Jan Rub´ın Supervisor: Ing. Josef Kokeˇs 1st May 2018 Acknowledgements First and foremost, I would like to express my sincere gratitude to my thesis supervisor, Ing. Josef Kokeˇs,for his guidance, engagement, extensive know- ledge, and willingness to meet at our countless consultations. I would also like to thank my brother, Tom´aˇsRub´ın,for proofreading my thesis. I cannot express enough gratitude towards my parents, Lenka and Jaroslav Rub´ınovi, who supported me both morally and financially through my whole studies. Last but not least, this thesis would not be possible without Anna who re- lentlessly supported me when I needed it most. Declaration I hereby declare that the presented thesis is my own work and that I have cited all sources of information in accordance with the Guideline for adhering to ethical principles when elaborating an academic final thesis. -
SSL/TLS Interception Proxies and Transitive Trust Jeff Jarmoc Dell Secureworks Counter Threat Unit℠ Threat Intelligence
SSL/TLS Interception Proxies and Transitive Trust Jeff Jarmoc Dell SecureWorks Counter Threat Unit℠ Threat Intelligence Presented at Black Hat Europe – March 14, 2012. Introduction Secure Sockets Layer (SSL) [1] and its successor Transport Layer Security (TLS) [2] have become key components of the modern Internet. The privacy, integrity, and authenticity [3] [4] provided by these protocols are critical to allowing sensitive communications to occur. Without these systems, e- commerce, online banking, and business-to-business exchange of information would likely be far less frequent. Threat actors have also recognized the benefits of transport security, and they are increasingly turning to SSL to hide their activities. Advanced Persistent Threat (APT) attackers [5], botnets [6], and even commodity web attacks can leverage SSL encryption to evade detection. To counter these tactics, organizations are increasingly deploying security controls that intercept end- to-end encrypted channels. Web proxies, data loss prevention (DLP) systems, specialized threat detection solutions, and network intrusion prevention systems (NIPS) offer functionality to intercept, inspect, and filter encrypted traffic. Similar functionality is present in lawful intercept systems and solutions enabling the broad surveillance of encrypted communications by governments. Broadly classified as “SSL/TLS interception proxies,” these solutions act as a “man in the middle,” violating the end-to-end security promises of SSL. This type of interception comes at a cost. Intercepting SSL-encrypted connections sacrifices a degree of privacy and integrity for the benefit of content inspection, often at the risk of authenticity and endpoint validation. Implementers and designers of SSL interception proxies should consider these risks and understand how their systems operate in unusual circumstances. -
Is Bob Sending Mixed Signals?
Is Bob Sending Mixed Signals? Michael Schliep Ian Kariniemi Nicholas Hopper University of Minnesota University of Minnesota University of Minnesota [email protected] [email protected] [email protected] ABSTRACT Demand for end-to-end secure messaging has been growing rapidly and companies have responded by releasing applications that imple- ment end-to-end secure messaging protocols. Signal and protocols based on Signal dominate the secure messaging applications. In this work we analyze conversational security properties provided by the Signal Android application against a variety of real world ad- versaries. We identify vulnerabilities that allow the Signal server to learn the contents of attachments, undetectably re-order and drop messages, and add and drop participants from group conversations. We then perform proof-of-concept attacks against the application to demonstrate the practicality of these vulnerabilities, and suggest mitigations that can detect our attacks. The main conclusion of our work is that we need to consider more than confidentiality and integrity of messages when designing future protocols. We also stress that protocols must protect against compromised servers and at a minimum implement a trust but verify model. 1 INTRODUCTION (a) Alice’s view of the conversa-(b) Bob’s view of the conversa- Recently many software developers and companies have been inte- tion. tion. grating end-to-end encrypted messaging protocols into their chat applications. Some applications implement a proprietary protocol, Figure 1: Speaker inconsistency in a conversation. such as Apple iMessage [1]; others, such as Cryptocat [7], imple- ment XMPP OMEMO [17]; but most implement the Signal protocol or a protocol based on Signal, including Open Whisper Systems’ caching. -
Spring 2009 Edition of Genesis V Alumni Magazine
theGenesis alumni magazine of saint ignatius college preparatory Vspring 2009 1 Joe Boswell ’02 and Kate Brandt ’03, who both work in the Obama Administration, are pictured here in the historic Indian Treaty Room in the Eisenhower Office Building with the White House in the background. Read about them on pages 35 and 38. AttleePhotography.com. genesis v A Report to Concerned Individuals Vol. 46, No. 1 Spring 2009 Administration Rev. Robert T. Walsh, S.J. President Mr. Joseph A. Vollert Vice President for Development Mr. Patrick Ruff Principal Rev. Thomas H. O’Neill, S.J. Superior Mr. John J. Ring Director of Alumni Relations Ms. Marielle A. Murphy Associate Director of Development Mrs. Cynthia Fitzgibbon Director of Special Events Mr. Fred L. Tocchini Director of Special Projects Mr. John J. Grealish Business Manager Editorial Staff Mr. Paul J. Totah Editor Arthur Cecchin Sports Editor Nancy Barisic Layout & Design Douglas A. Salin Photo Editor GENESIS V (USPS 899-060) is published quarterly by St. Ignatius College Preparatory, 2001 37th Avenue, San Francisco, CA 94116-9981. Periodicals Postage Paid at San Francisco, CA, and at additional mailing offices. POSTMASTER: Send address changes to GENE SIS V, 2001 37th Avenue, San Francisco, CA 94116-9981. CONTACT US: You can send e-mail to [email protected] or reach us at (415) 731-7500 ext. 206. You can also read the issue on our web site at www.siprep.org/genesis. ST. IGNATIUS, mindful of its mission to be witness to the love of Christ for all, admits students of any race, color and national and/or ethnic origin to all the rights, privileges, programs and activities generally accorded to or made available to students at this school. -
Computer Security
CSE 40567 / 60567: Computer Security Network Security 1 !1 Homework #5 is due tonight at 11:59PM (your timezone) See Assignments Page on the course website for details !2 Live Tuesday in Class RC Johnson (PayPal) (Will not be recorded) !3 Course Roadmap Basics The Web (weeks 1 & 2) (weeks 15 & 16) 3 Core Areas (weeks 3 - 6) (weeks 6 - 10) (weeks 11 - 15) !4 Heartbleed What is it? Serious input validation vulnerability in OpenSSL Bug introduced: OpenSSL version 1.0.1 on March 14, 2012 Bug disclosed: April 7th, 2014 Protocol affected: TLS • Successor to SSL • Meant to secure network traffic from eavesdropping attacks • Good example of security software making things less secure http://heartbleed.com/ !5 Heartbleed bug explained A depiction of Heartbleed BY-SA 3.0 FenixFeather !6 The bug in OpenSSL p is a pointer to start of message /* Read type and payload length first */ hbtype = *p++; No bounds checking to enforce n2s(p, payload); consistency between pl = p; payload_length and the actual payload The fix: hbtype = *p++; n2s(p, payload); if (1 + 2 + payload + 16 > s->s3->rrec.length) return 0; /* silently discard per RFC 6520 sec. 4 */ pl = p; !7 Scope of the vulnerability 700 525 350 175 0 8 April, 2014, 4PM UTC 9 April, 2014, 7:30AM UTC 10 April, 2014, 12:30AM UTC Vulnerable Websites Among the Top 10,000 Among the Top Websites Vulnerable !8 Response from the community "OpenSSL is not developed by a responsible team." - Theo de Raadt Large mistake: OpenSSL developers wrote their own memory management routines, circumventing library protections -
The Most Dangerous Code in the World: Validating SSL Certificates In
The Most Dangerous Code in the World: Validating SSL Certificates in Non-Browser Software Martin Georgiev Subodh Iyengar Suman Jana The University of Texas Stanford University The University of Texas at Austin at Austin Rishita Anubhai Dan Boneh Vitaly Shmatikov Stanford University Stanford University The University of Texas at Austin ABSTRACT cations. The main purpose of SSL is to provide end-to-end security SSL (Secure Sockets Layer) is the de facto standard for secure In- against an active, man-in-the-middle attacker. Even if the network ternet communications. Security of SSL connections against an is completely compromised—DNS is poisoned, access points and active network attacker depends on correctly validating public-key routers are controlled by the adversary, etc.—SSL is intended to certificates presented when the connection is established. guarantee confidentiality, authenticity, and integrity for communi- We demonstrate that SSL certificate validation is completely bro- cations between the client and the server. Authenticating the server is a critical part of SSL connection es- ken in many security-critical applications and libraries. Vulnerable 1 software includes Amazon’s EC2 Java library and all cloud clients tablishment. This authentication takes place during the SSL hand- based on it; Amazon’s and PayPal’s merchant SDKs responsible shake, when the server presents its public-key certificate. In order for transmitting payment details from e-commerce sites to payment for the SSL connection to be secure, the client must carefully verify gateways; integrated shopping carts such as osCommerce, ZenCart, that the certificate has been issued by a valid certificate authority, Ubercart, and PrestaShop; AdMob code used by mobile websites; has not expired (or been revoked), the name(s) listed in the certifi- Chase mobile banking and several other Android apps and libraries; cate match(es) the name of the domain that the client is connecting Java Web-services middleware—including Apache Axis, Axis 2, to, and perform several other checks [14, 15]. -
Colloquium Poster 32 Series
THIRTY SECOND SERIES Spring 2010 Thursdays at 12:00 noon Salazar 2016 FEB. 11 Joe Dupre, Sonoma State University, IT Information Security Management in the Enterprise Information and knowledge are valuable and worth protecting. We need efficient methods of protection in large homogenous environments. How do you get smart people with divergent ideas moving in the same direction on information security? Do the following: strategic alignment, risk management on all issues, provide value - reduce support costs, enhance competitive stance, assure success of strategy deployment resource management - people, technology, process assurance process integration - get connected and involved with other security groups in your enterprise. Performance measures - Did we do what we set out to do, does the data indicate we should be doing something else? Multiuse of metrics. This talk is based on the curriculum for the ISACA.org Certified Information Security Manager (CISM) certification. Pizza after talk in Darwin 28 FEB. 18 John Davis, Microsoft Research, Mountain View BEE3: Silly Putty for Computer Scientists! Parallel computing for the masses has arrived. Unfortunately, software, tools, research, and pedagogy are lagging behind with only niche successful parallel applications existing, print statements still being used for debugging, research limited to using existing platforms, and few colleges and universities offering parallel programming and computer architecture classes for undergraduates. Let me present BEE3, the Berkeley Emulation Engine, version 3. BEE3 is a reconfigurable computing platform that we are using to target three main research areas: Computer Architecture, Systems, and Application Acceleration. Using these examples, I will demonstrate how we are using reconfigurable computing systems to help build parallel software and tools, conduct fundamental research, and provide a pedagogical platform. -
Multi-Device Secure Instant Messaging
SoK: Multi-Device Secure Instant Messaging Antonio Dimeo, Felix Gohla, Daniel Goßen, Niko Lockenvitz {antonio.dimeo, felix.gohla, daniel.gossen, niko.lockenvitz}@student.hpi.de Hasso Plattner Institute, University of Potsdam April 17, 2021 Abstract The secure multi-device instant messaging ecosystem is diverse, varied, and under- represented in academia. We create a systematization of knowledge which focuses on the challenges of multi-device messaging in a secure context and give an overview of the current situation in the multi-device setting. For that, we analyze messenger documentation, white papers, and research that deals with multi-device messaging. This includes a detailed description of different patterns for data transfer between devices as well as device management, i.e. how clients are cryptographically linked or unlinked to or from an account and how the initial setup can be implemented. We then evaluate different instant messengers with regard to relevant criteria, e.g. whether they achieve specific security, usability, and privacy goals. In the end, we outline interesting areas for future research. Contents 1 Introduction3 1.1 Group Messaging vs. Multi-Device Messaging............... 4 1.2 Methodology.................................. 4 2 Multi-Device Messaging7 2.1 Context...................................... 7 2.2 Transferring Data Between Different Devices of One User........ 7 2.2.1 Storing Data on a Server........................ 8 2.2.2 Using Messages to Exchange Data.................. 9 2.3 Transferring Data to a Different User..................... 11 2.3.1 Without End-to-end Encryption................... 11 2.3.2 End-to-end Encryption With Shared Group Key.......... 13 2.3.3 End-to-end Encryption Per Recipient............... -
Good Practice Guide on Vulnerability Disclosure from Challenges to Recommendations
Good Practice Guide on Vulnerability Disclosure From challenges to recommendations NOVEMBER 2015 www.enisa.europa.eu European Union Agency For Network And Information Security Good Practice Guide on Vulnerability Disclosure Creation date: November 15 About ENISA The European Union Agency for Network and Information Security (ENISA) is a centre of network and information security expertise for the European Union (EU), its member states, the private sector and Europe’s citizens. ENISA works with these groups to develop advice and recommendations on good practice in information security. It assists EU member states in implementing relevant EU legislation and works to improve the resilience of Europe’s critical information infrastructure and networks. ENISA seeks to enhance existing expertise in EU member states by supporting the development of cross-border communities committed to improving network and information security throughout the EU. More information about ENISA and its work can be found at www.enisa.europa.eu. Authors This document was created by the CERT Capability team at ENISA in consultation with RAND Europe Project officer Cosmin Ciobanu Contact To contact the authors please use [email protected] For media enquiries about this report, please use [email protected]. Acknowledgements The project team wishes to thank all the interviewees, and those who provided written input for the project, for their time and invaluable insights. Their contribution to this project has been essential. 02 Good Practice Guide on Vulnerability Disclosure Creation date: November 15 Legal notice Notice must be taken that this publication represents the views and interpretations of the authors and editors, unless stated otherwise. -
Hack Proofing Your Network, Second Edition
194_HP_Net2e_FC 2/22/02 10:01 AM Page 1 1 YEAR UPGRADE BUYER PROTECTION PLAN ™ The Only Way to Stop a Hacker is to Think Like One David R. Mirza Ahmad Dan “Effugas” Kaminsky Ido Dubrawsky F. William Lynch Hal Flynn Steve W. Manzuik Joseph “Kingpin” Grand Ryan Permeh Robert Graham Ken Pfeil Norris L. Johnson, Jr. Rain Forest Puppy K2 Ryan Russell Technical Editor UPDATED BESTSELLER! 194_HPYN2e_FM.qxd 2/15/02 2:36 PM Page i [email protected] With more than 1,500,000 copies of our MCSE, MCSD, CompTIA, and Cisco study guides in print, we continue to look for ways we can better serve the information needs of our readers. One way we do that is by listening. Readers like yourself have been telling us they want an Internet-based ser- vice that would extend and enhance the value of our books. Based on reader feedback and our own strategic plan, we have created a Web site that we hope will exceed your expectations. [email protected] is an interactive treasure trove of useful infor- mation focusing on our book topics and related technologies. The site offers the following features: I One-year warranty against content obsolescence due to vendor product upgrades. You can access online updates for any affected chapters. I “Ask the Author” customer query forms that enable you to post questions to our authors and editors. I Exclusive monthly mailings in which our experts provide answers to reader queries and clear explanations of complex material. I Regularly updated links to sites specially selected by our editors for readers desiring additional reliable information on key topics.