Understanding and Mitigating Attacks Targeting Web Browsers

Total Page:16

File Type:pdf, Size:1020Kb

Understanding and Mitigating Attacks Targeting Web Browsers Understanding and Mitigating Attacks Targeting Web Browsers A Dissertation presented in partial fulfillment of the requirements for the degree of Doctor of Philosophy in the field of Information Assurance by Ahmet Salih Buyukkayhan Northeastern University Khoury College of Computer Sciences Boston, Massachusetts April 2019 To my family, teachers and mentors. i Contents List of Figures v List of Tables vii Acknowledgments viii Abstract of the Dissertation ix 1 Introduction 1 1.1 Structure of the Thesis . .2 2 Background 4 2.1 Browser Extensions . .4 2.1.1 Firefox Extensions . .5 2.1.2 Extension Security . .7 2.2 Vulnerabilities in Web Applications . .9 2.2.1 Vulnerability Reward Programs and Platforms . .9 2.2.2 XSS Vulnerabilities . 10 2.2.3 XSS Defenses . 12 3 CrossFire: Firefox Extension-Reuse Vulnerabilities 14 3.1 Overview . 14 3.2 Threat Model . 15 3.3 Design . 16 3.3.1 Vulnerability Analysis . 17 3.3.2 Exploit Generation . 19 3.3.3 Example Vulnerabilities . 20 3.4 Implementation . 23 3.5 Evaluation . 23 3.5.1 Vulnerabilities in Top Extensions . 23 3.5.2 Random Sample Study of Extensions . 25 3.5.3 Performance & Manual Effort . 27 ii 3.5.4 Case Study: Submitting an Extension to Mozilla Add-ons Repository . 28 3.5.5 Jetpack Extensions. 30 3.5.6 Implications on Extension Vetting Procedures . 31 3.6 Summary . 31 4 SENTINEL: Securing Legacy Firefox Extensions 33 4.1 Overview . 33 4.2 Threat Model . 34 4.3 Design . 35 4.3.1 Intercepting XPCOM Operations . 36 4.3.2 Intercepting XUL Document Manipulations . 37 4.3.3 Preventing Namespace Collision Exploits . 40 4.3.4 Policy Manager . 41 4.3.5 Limitations . 43 4.4 Implementation . 43 4.4.1 Proxy Objects . 43 4.4.2 XPCOM Objects as Method Arguments . 45 4.4.3 XUL Elements without an ID . 45 4.4.4 Modifications to the Browser and Extensions . 46 4.5 Evaluation . 48 4.5.1 Policy Examples . 48 4.5.2 Runtime Performance . 56 4.5.3 Applicability of the Solution . 57 4.5.4 Falsely Blocked Legitimate Extensions . 58 4.6 Summary . 59 5 An Empirical Analysis of XSS Exploitation Techniques 60 5.1 Overview . 60 5.2 Methodology . 63 5.2.1 Data Collection . 63 5.2.2 Feature Selection . 65 5.2.3 Exploit String Extraction . 66 5.2.4 Static Feature Extraction . 68 5.2.5 Exploit Execution . 69 5.2.6 Dynamic Feature Extraction . 71 5.2.7 Data Integration and Filtering . 72 5.2.8 Validation . 73 5.3 Analysis . 74 5.3.1 Affected Websites . 76 5.3.2 Sink Analysis . 77 5.3.3 XSS Filters . 79 5.3.4 Exploit Analysis . 81 iii 5.3.5 Exploit Patterns . 88 5.3.6 Exploit Sophistication . 90 5.3.7 Exploit Authors . 92 5.4 Summary . 95 6 Papers 96 6.1 Thesis Publications . 96 6.2 Other Publications . 96 7 Conclusion 99 Bibliography 101 iv List of Figures 3.1 An overview of the core components of CROSSFIRE................. 17 3.2 Breakdown of true positive vulnerabilities discovered by CROSSFIRE by category. 26 3.3 Screenshots from Mozilla Add-ons website showing the accepted extension and its fully reviewed status. 28 4.1 Overview of SENTINEL from the user’s perspective. 35 4.2 An overview of SENTINEL, demonstrating how a file deletion operation can be intercepted and checked with a policy. 37 4.3 Implementation of the Object Proxy using a proxy construct. 44 4.4 A malicious extension can redirect users visiting “https://www.bankofamerica.com” to a different website “http://example.com” and fake the browser identity indicators. 51 5.1 Overview of our static and dynamic analysis system. 64 5.2 Quarterly exploit submissions and unique affected domains in XSSED (outer) and OPENBUGBOUNTY (inset). Most new submissions are found on new domains, suggesting a large supply of vulnerable domains on the Web. 75 5.3 Quarterly distribution of the popularity of domains affected by exploit submissions (XSSED left, OPENBUGBOUNTY right). Domains grouped by popularity accord- ing to their Alexa ranks; the last interval includes unranked domains. More than half of submissions are for unpopular websites. The rank interval distribution is al- most uniform over time, illustrating that XSS vulnerabilities continue to be found even on the most popular websites. 76 5.4 Quarterly tag and event handler market share in OPENBUGBOUNTY. Submissions of script tags decline in favor of other tags with event handlers. 84 5.5 CDF of sophistication scores. XSSED submissions tend to have lower scores than OPENBUGBOUNTY, and less score diversity due to fewer patterns. 85 5.6 Quarterly median sophistication score for all submissions and for distinct exploit patterns in OPENBUGBOUNTY. Inset shows XSSED data. 85 v 5.7 Correlation matrix of exploitation techniques and selected tags and attributes for (a) XSSED and (b) OPENBUGBOUNTY. Use of <script> is negatively corre- lated with most other techniques, meaning they are used alternatively. The popular exploit pattern <img src=# onerror> is visible as the pairwise correlation between <img>, src, and F2. Rarely used techniques such as I1 and O3, or I2 and F4, may be correlated because most uses occur in similar submissions by the same author. 88 5.8 CDF of exploit sophistication according to author productivity. Low productivity users contribute fewer low score exploits, causing a higher median. 93 5.9 Difference between the lowest and highest scored exploit per user with 10+ sub- missions (CDF). Most users submit exploits of varying sophistication. 94 5.10 CDF of the median and max. sophistication score per author. The most productive users are aware of sophisticated techniques, but use them sparingly. 94 vi List of Tables 3.1 Examples of security-sensitive XPCOM and browser APIs used by CROSSFIRE as data-flow sinks during vulnerability analysis. 18 3.2 Detailed analysis results of the top 10 Firefox extensions. 24 3.3 Five-number summaries, mean, and total values of CROSSFIRE’s static analysis results. The experiment is performed on the top 2,000 Firefox extensions. 24 3.4 Summary of the true and false positives detected by CROSSFIRE when analyzing 323 extensions randomly sampled from top 2,000 Firefox extensions. 25 3.5 Five-number summaries and the mean time measurements of automatic static anal- ysis by CROSSFIRE, and human analysis to craft working exploits from exploit templates. 27 4.1 Runtime overhead imposed by SENTINEL on Firefox when running popular exten- sions. 57 4.2 The percentage of Jetpack and legacy extensions among the top 1,000 popular Firefox extensions. 57 5.1 Raw XSS Data Collected (before filtering). 64 5.2 Examples for exploitation techniques excluded due to very low occurrence (func- tionally equivalent to alert(1))........................... 66 5.3 Exploits Executed by Triggering Events . 69 5.4 Validation of Static and Dynamic Feature Extraction . 73 5.5 Exploits blocked by XSS filters (HTTP GET only) . 80 5.6 Aggregated Use of Exploitation Techniques . 82 5.7 Detected Exploitation Techniques by Category. ( static, dynamic, combined detection methodology; percentages for XSSED G#/OPENBH#UGBOUNTY )...... 87 5.8 Most Common Exploit Patterns (ordered by submissions; rank for author use in second column) . 89 5.9 The Top 5 Exploits by Sophistication Score . 91 vii Acknowledgments This thesis is written with the support, mentorship, and encouragement given to me by many people. I would like to first thank my advisor Prof. Engin Kirda who helped me to discover my interests in security research during my undergrad years and then offered me the opportunity to pursue Ph.D. in cybersecurity at Northeastern. I am also thankful to Prof. William Robertson and Prof. Engin Kirda for their guidance, mentorship, and support in every stage of my Ph.D. I thank my committee members Prof. Gianluca Stringhini and Prof. Alina Oprea for patiently reading this thesis and providing valuable comments and feedbacks. I owe a special gratitude to Prof. Alina Oprea for advising me on the projects we.
Recommended publications
  • Differential Fuzzing the Webassembly
    Master’s Programme in Security and Cloud Computing Differential Fuzzing the WebAssembly Master’s Thesis Gilang Mentari Hamidy MASTER’S THESIS Aalto University - EURECOM MASTER’STHESIS 2020 Differential Fuzzing the WebAssembly Fuzzing Différentiel le WebAssembly Gilang Mentari Hamidy This thesis is a public document and does not contain any confidential information. Cette thèse est un document public et ne contient aucun information confidentielle. Thesis submitted in partial fulfillment of the requirements for the degree of Master of Science in Technology. Antibes, 27 July 2020 Supervisor: Prof. Davide Balzarotti, EURECOM Co-Supervisor: Prof. Jan-Erik Ekberg, Aalto University Copyright © 2020 Gilang Mentari Hamidy Aalto University - School of Science EURECOM Master’s Programme in Security and Cloud Computing Abstract Author Gilang Mentari Hamidy Title Differential Fuzzing the WebAssembly School School of Science Degree programme Master of Science Major Security and Cloud Computing (SECCLO) Code SCI3084 Supervisor Prof. Davide Balzarotti, EURECOM Prof. Jan-Erik Ekberg, Aalto University Level Master’s thesis Date 27 July 2020 Pages 133 Language English Abstract WebAssembly, colloquially known as Wasm, is a specification for an intermediate representation that is suitable for the web environment, particularly in the client-side. It provides a machine abstraction and hardware-agnostic instruction sets, where a high-level programming language can target the compilation to the Wasm instead of specific hardware architecture. The JavaScript engine implements the Wasm specification and recompiles the Wasm instruction to the target machine instruction where the program is executed. Technically, Wasm is similar to a popular virtual machine bytecode, such as Java Virtual Machine (JVM) or Microsoft Intermediate Language (MSIL).
    [Show full text]
  • Rich Media Web Application Development I Week 1 Developing Rich Media Apps Today’S Topics
    IGME-330 Rich Media Web Application Development I Week 1 Developing Rich Media Apps Today’s topics • Tools we’ll use – what’s the IDE we’ll be using? (hint: none) • This class is about “Rich Media” – we’ll need a “Rich client” – what’s that? • Rich media Plug-ins v. Native browser support for rich media • Who’s in charge of the HTML5 browser API? (hint: no one!) • Where did HTML5 come from? • What are the capabilities of an HTML5 browser? • Browser layout engines • JavaScript Engines Tools we’ll use • Browsers: • Google Chrome - assignments will be graded on Chrome • Safari • Firefox • Text Editor of your choice – no IDE necessary • Adobe Brackets (available in the labs) • Notepad++ on Windows (available in the labs) • BBEdit or TextWrangler on Mac • Others: Atom, Sublime • Documentation: • https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model • https://developer.mozilla.org/en-US/docs/Web/API/Canvas_API/Tutorial • https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide What is a “Rich Client” • A traditional “web 1.0” application needs to refresh the entire page if there is even the smallest change to it. • A “rich client” application can update just part of the page without having to reload the entire page. This makes it act like a desktop application - see Gmail, Flickr, Facebook, ... Rich Client programming in a web browser • Two choices: • Use a plug-in like Flash, Silverlight, Java, or ActiveX • Use the built-in JavaScript functionality of modern web browsers to access the native DOM (Document Object Model) of HTML5 compliant web browsers.
    [Show full text]
  • Flash Player and Linux
    Flash Player and Linux Ed Costello Engineering Manager Adobe Flash Player Tinic Uro Sr. Software Engineer Adobe Flash Player 2007 Adobe Systems Incorporated. All Rights Reserved. Overview . History and Evolution of Flash Player . Flash Player 9 and Linux . On the Horizon 2 2007 Adobe Systems Incorporated. All Rights Reserved. Flash on the Web: Yesterday 3 2006 Adobe Systems Incorporated. All Rights Reserved. Flash on the Web: Today 4 2006 Adobe Systems Incorporated. All Rights Reserved. A Brief History of Flash Player Flash Flash Flash Flash Linux Player 5 Player 6 Player 7 Player 9 Feb 2001 Dec 2002 May 2004 Jan 2007 Win/ Flash Flash Flash Flash Flash Flash Flash Mac Player 3 Player 4 Player 5 Player 6 Player 7 Player 8 Player 9 Sep 1998 Jun 1999 Aug 2000 Mar 2002 Sep 2003 Aug 2005 Jun 2006 … Vector Animation Interactivity “RIAs” Developers Expressive Performance & Video & Standards Simple Actions, ActionScript Components, ActionScript Filters, ActionScript 3.0, Movie Clips, 1.0 Video (H.263) 2.0 Blend Modes, New virtual Motion Tween, (ECMAScript High-!delity machine MP3 ed. 3), text, Streaming Video (ON2) video 5 2007 Adobe Systems Incorporated. All Rights Reserved. Widest Reach . Ubiquitous, cross-platform, rich media and rich internet application runtime . Installed on 98% of internet- connected desktops1 . Consistently reaches 80% penetration within 12 months of release2 . Flash Player 9 reached 80%+ penetration in <9 months . YUM-savvy updater to support rapid/consistent Linux penetration 1. Source: Millward-Brown September 2006. Mature Market data. 2. Source: NPD plug-in penetration study 6 2007 Adobe Systems Incorporated. All Rights Reserved.
    [Show full text]
  • Browser Wars
    Uppsala universitet Inst. för informationsvetenskap Browser Wars Kampen om webbläsarmarknaden Andreas Högström, Emil Pettersson Kurs: Examensarbete Nivå: C Termin: VT-10 Datum: 2010-06-07 Handledare: Anneli Edman "Anyone who slaps a 'this page is best viewed with Browser X' label on a Web page appears to be yearning for the bad old days, before the Web, when you had very little chance of read- ing a document written on another computer, another word processor, or another network" - Sir Timothy John Berners-Lee, grundare av World Wide Web Consortium, Technology Review juli 1996 Innehållsförteckning Abstract ...................................................................................................................................... 1 Sammanfattning ......................................................................................................................... 2 1 Inledning .................................................................................................................................. 3 1.1 Bakgrund .............................................................................................................................. 3 1.2 Syfte ..................................................................................................................................... 3 1.3 Frågeställningar .................................................................................................................... 3 1.4 Avgränsningar .....................................................................................................................
    [Show full text]
  • Security Analytics for Enterprise Threat Detection
    MADE: Security Analytics for Enterprise Threat Detection Alina Oprea Zhou Li Northeastern University University of California, Irvine [email protected] [email protected] Robin Norris Kevin Bowers EMC/Dell CIRC RSA [email protected] [email protected] ABSTRACT These concerns affect not only individuals, but enterprises as well. Enterprises are targeted by various malware activities at a staggering The enterprise perimeter is only as strong as its weakest link and rate. To counteract the increased sophistication of cyber attacks, that boundary is becoming increasingly fuzzy with the prevalence most enterprises deploy within their perimeter a number of secu- of remote workers using company-issued computers on networks rity technologies, including firewalls, anti-virus software, and web outside of the enterprise control. Enterprises attempt to combat cyber proxies, as well as specialized teams of security analysts forming attacks by deploying firewalls, anti-virus agents, web proxies and Security Operations Centers (SOCs). other security technologies, but these solutions cannot detect or In this paper we address the problem of detecting malicious ac- respond to all malware. Large organizations employ “hunters” or tivity in enterprise networks and prioritizing the detected activities tier 3 analysts (part of the enterprise Security Operations Center – according to their risk. We design a system called MADE using ma- SOC) [44] to search for malicious behavior that has evaded their chine learning applied to data extracted from security logs. MADE automated tools. Unfortunately, this solution is not scalable, both due leverages an extensive set of features for enterprise malicious com- to the lack of qualified people and the rate at which such malware is munication and uses supervised learning in a novel way for prior- invading the enterprise.
    [Show full text]
  • Operation Black Atlas
    A TrendLabs Report Operation Black Atlas How Modular Botnets are Used in PoS Attacks TrendLabs Security Intelligence Blog Jay Yaneza and Erika Mendoza Trend Micro Cyber Safety Solutions Team December 2015 Trend Micro | Operation Black Atlas: How Modular Botnets are Used in Attacks Contents Introduction ............................................................................................................ 3 Technical Details ................................................................................................... 3 Probing and Penetrating the Environment ......................................................... 3 Point-of-Sale Threats ......................................................................................... 5 New Items in NewPosThings ............................................................................. 7 Use of Known PoS Malware Threats ............................................................... 10 Gorynych or Diamond Fox ............................................................................... 13 Spy Net RAT .................................................................................................... 20 Victimology .......................................................................................................... 21 Attribution ............................................................................................................ 23 Conclusion ........................................................................................................... 25 TREND MICRO LEGAL
    [Show full text]
  • Behavioural Analysis of Tracing JIT Compiler Embedded in the Methodical Accelerator Design Software
    Scuola Politecnica e delle Scienze di Base Corso di Laurea Magistrale in Ingegneria Informatica Tesi di laurea magistrale in Calcolatori Elettronici II Behavioural Analysis of Tracing JIT Compiler Embedded in the Methodical Accelerator Design Software Anno Accademico 2018/2019 CERN-THESIS-2019-152 //2019 relatori Ch.mo prof. Nicola Mazzocca Ch.mo prof. Pasquale Arpaia correlatore Ing. Laurent Deniau PhD candidato Dario d’Andrea matr. M63000695 Acknowledgements Firstly, I would like to thank my supervisor at CERN, Laurent Deniau, for his daily support and his useful suggestions throughout the work described in this thesis. I would like to express my gratitude to both my university supervisors, Nicola Mazzocca and Pasquale Arpaia, for their helpfulness during this work and for their support during the past years at university. I feel privileged of being allowed to work with such inspiring mentors. This thesis would not have been possible without the help from the community of the LuaJIT project including all the useful insights contained in its mailing list, specially by its author, Mike Pall, who worked for many years accomplishing an amazing job. A special acknowledgement should be addressed to my family. I thank my father Guido and my mother Leda who guided me with love during my education and my life. I am grateful to my brother Fabio, my grandmother Tina, and my uncle Nicola, for their support during the past years. I also want to remember my uncle Bruno who inspired me for my academic career. I wish to express my deepest gratitude to Alicia for her unconditional encour- agement.
    [Show full text]
  • Mozilla Source Tree Docs Release 50.0A1
    Mozilla Source Tree Docs Release 50.0a1 August 02, 2016 Contents 1 SSL Error Reporting 1 2 Firefox 3 3 Telemetry Experiments 11 4 Build System 17 5 WebIDL 83 6 Graphics 85 7 Firefox for Android 87 8 Indices and tables 99 9 Localization 101 10 mach 105 11 CloudSync 113 12 TaskCluster Task-Graph Generation 119 13 Crash Manager 133 14 Telemetry 137 15 Crash Reporter 207 16 Supbrocess Module 211 17 Toolkit modules 215 18 Add-on Manager 221 19 Linting 227 20 Indices and tables 233 21 Mozilla ESLint Plugin 235 i 22 Python Packages 239 23 Managing Documentation 375 24 Indices and tables 377 Python Module Index 379 ii CHAPTER 1 SSL Error Reporting With the introduction of HPKP, it becomes useful to be able to capture data on pin violations. SSL Error Reporting is an opt-in mechanism to allow users to send data on such violations to mozilla. 1.1 Payload Format An example report: { "hostname":"example.com", "port":443, "timestamp":1413490449, "errorCode":-16384, "failedCertChain":[ ], "userAgent":"Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0", "version":1, "build":"20141022164419", "product":"Firefox", "channel":"default" } Where the data represents the following: “hostname” The name of the host the connection was being made to. “port” The TCP port the connection was being made to. “timestamp” The (local) time at which the report was generated. Seconds since 1 Jan 1970, UTC. “errorCode” The error code. This is the error code from certificate veri- fication. Here’s a small list of the most commonly-encountered errors: https://wiki.mozilla.org/SecurityEngineering/x509Certs#Error_Codes_in_Firefox In theory many of the errors from sslerr.h, secerr.h, and pkixnss.h could be encountered.
    [Show full text]
  • Security Analysis of Firefox Webextensions
    6.857: Computer and Network Security Due: May 16, 2018 Security Analysis of Firefox WebExtensions Srilaya Bhavaraju, Tara Smith, Benny Zhang srilayab, tsmith12, felicity Abstract With the deprecation of Legacy addons, Mozilla recently introduced the WebExtensions API for the development of Firefox browser extensions. WebExtensions was designed for cross-browser compatibility and in response to several issues in the legacy addon model. We performed a security analysis of the new WebExtensions model. The goal of this paper is to analyze how well WebExtensions responds to threats in the previous legacy model as well as identify any potential vulnerabilities in the new model. 1 Introduction Firefox release 57, otherwise known as Firefox Quantum, brings a large overhaul to the open-source web browser. Major changes with this release include the deprecation of its initial XUL/XPCOM/XBL extensions API to shift to its own WebExtensions API. This WebExtensions API is currently in use by both Google Chrome and Opera, but Firefox distinguishes itself with further restrictions and additional functionalities. Mozilla’s goals with the new extension API is to support cross-browser extension development, as well as offer greater security than the XPCOM API. Our goal in this paper is to analyze how well the WebExtensions model responds to the vulnerabilities present in legacy addons and discuss any potential vulnerabilities in the new model. We present the old security model of Firefox extensions and examine the new model by looking at the structure, permissions model, and extension review process. We then identify various threats and attacks that may occur or have occurred before moving onto recommendations.
    [Show full text]
  • Cross Site Scripting Attacks Xss Exploits and Defense.Pdf
    436_XSS_FM.qxd 4/20/07 1:18 PM Page ii 436_XSS_FM.qxd 4/20/07 1:18 PM Page i Visit us at www.syngress.com Syngress is committed to publishing high-quality books for IT Professionals and deliv- ering those books in media and formats that fit the demands of our customers. We are also committed to extending the utility of the book you purchase via additional mate- rials available from our Web site. SOLUTIONS WEB SITE To register your book, visit www.syngress.com/solutions. Once registered, you can access our [email protected] Web pages. There you may find an assortment of value- added features such as free e-books related to the topic of this book, URLs of related Web sites, FAQs from the book, corrections, and any updates from the author(s). ULTIMATE CDs Our Ultimate CD product line offers our readers budget-conscious compilations of some of our best-selling backlist titles in Adobe PDF form. These CDs are the perfect way to extend your reference library on key topics pertaining to your area of expertise, including Cisco Engineering, Microsoft Windows System Administration, CyberCrime Investigation, Open Source Security, and Firewall Configuration, to name a few. DOWNLOADABLE E-BOOKS For readers who can’t wait for hard copy, we offer most of our titles in downloadable Adobe PDF form. These e-books are often available weeks before hard copies, and are priced affordably. SYNGRESS OUTLET Our outlet store at syngress.com features overstocked, out-of-print, or slightly hurt books at significant savings. SITE LICENSING Syngress has a well-established program for site licensing our e-books onto servers in corporations, educational institutions, and large organizations.
    [Show full text]
  • Visual Validation of SSL Certificates in the Mozilla Browser Using Hash Images
    CS Senior Honors Thesis: Visual Validation of SSL Certificates in the Mozilla Browser using Hash Images Hongxian Evelyn Tay [email protected] School of Computer Science Carnegie Mellon University Advisor: Professor Adrian Perrig Electrical & Computer Engineering Engineering & Public Policy School of Computer Science Carnegie Mellon University Monday, May 03, 2004 Abstract Many internet transactions nowadays require some form of authentication from the server for security purposes. Most browsers are presented with a certificate coming from the other end of the connection, which is then validated against root certificates installed in the browser, thus establishing the server identity in a secure connection. However, an adversary can install his own root certificate in the browser and fool the client into thinking that he is connected to the correct server. Unless the client checks the certificate public key or fingerprint, he would never know if he is connected to a malicious server. These alphanumeric strings are hard to read and verify against, so most people do not take extra precautions to check. My thesis is to implement an additional process in server authentication on a browser, using human recognizable images. The process, Hash Visualization, produces unique images that are easily distinguishable and validated. Using a hash algorithm, a unique image is generated using the fingerprint of the certificate. Images are easily recognizable and the user can identify the unique image normally seen during a secure AND accurate connection. By making a visual comparison, the origin of the root certificate is known. 1. Introduction: The Problem 1.1 SSL Security The SSL (Secure Sockets Layer) Protocol has improved the state of web security in many Internet transactions, but its complexity and neglect of human factors has exposed several loopholes in security systems that use it.
    [Show full text]
  • IT Acronyms.Docx
    List of computing and IT abbreviations /.—Slashdot 1GL—First-Generation Programming Language 1NF—First Normal Form 10B2—10BASE-2 10B5—10BASE-5 10B-F—10BASE-F 10B-FB—10BASE-FB 10B-FL—10BASE-FL 10B-FP—10BASE-FP 10B-T—10BASE-T 100B-FX—100BASE-FX 100B-T—100BASE-T 100B-TX—100BASE-TX 100BVG—100BASE-VG 286—Intel 80286 processor 2B1Q—2 Binary 1 Quaternary 2GL—Second-Generation Programming Language 2NF—Second Normal Form 3GL—Third-Generation Programming Language 3NF—Third Normal Form 386—Intel 80386 processor 1 486—Intel 80486 processor 4B5BLF—4 Byte 5 Byte Local Fiber 4GL—Fourth-Generation Programming Language 4NF—Fourth Normal Form 5GL—Fifth-Generation Programming Language 5NF—Fifth Normal Form 6NF—Sixth Normal Form 8B10BLF—8 Byte 10 Byte Local Fiber A AAT—Average Access Time AA—Anti-Aliasing AAA—Authentication Authorization, Accounting AABB—Axis Aligned Bounding Box AAC—Advanced Audio Coding AAL—ATM Adaptation Layer AALC—ATM Adaptation Layer Connection AARP—AppleTalk Address Resolution Protocol ABCL—Actor-Based Concurrent Language ABI—Application Binary Interface ABM—Asynchronous Balanced Mode ABR—Area Border Router ABR—Auto Baud-Rate detection ABR—Available Bitrate 2 ABR—Average Bitrate AC—Acoustic Coupler AC—Alternating Current ACD—Automatic Call Distributor ACE—Advanced Computing Environment ACF NCP—Advanced Communications Function—Network Control Program ACID—Atomicity Consistency Isolation Durability ACK—ACKnowledgement ACK—Amsterdam Compiler Kit ACL—Access Control List ACL—Active Current
    [Show full text]