DOCSLIB.ORG

Favocado: Fuzzing the Binding Code of Javascript Engines Using Semantically Correct Test Cases

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Favocado: Fuzzing the Binding Code of Javascript Engines Using Semantically Correct Test Cases Favocado: Fuzzing the Binding Code of JavaScript Engines Using Semantically Correct Test Cases Sung Ta Dinh∗, Haehyun Cho∗, Kyle Martiny, Adam Oestz, Kyle Zeng∗, Alexandros Kapravelosy, Gail-Joon Ahn∗x, Tiffany Bao∗, Ruoyu Wang∗, Adam Doupe´∗, and Yan Shoshitaishvili∗ ∗Arizona State University, yNorth Carolina State University, zPayPal, Inc., xSamsung Research ∗ftdsung, haehyun, zengyhkyle, gahn, tbao, fishw, doupe, [email protected] yfkdmarti2, [email protected], [email protected] Abstract—JavaScript runtime systems include some special- by the introduction of multiple JavaScript fuzzers over the past ized programming interfaces, called binding layers. Binding few years, none of which could be used to fuzz binding code layers translate data representations between JavaScript and in non-browser environments [24, 27, 29, 34, 37, 40, 41, 55, 56]. unsafe low-level languages, such as C and C++, by converting data However, due to the complexity in the implementation of between different types. Due to the wide adoption of JavaScript binding layers in JavaScript engines, vulnerabilities in these (and JavaScript engines) in the entire computing ecosystem, layers are not rare [11]. Therefore, there is a pressing need discovering bugs in JavaScript binding layers is critical. Nonethe- less, existing JavaScript fuzzers cannot adequately fuzz binding to design JavaScript fuzzers to efficiently fuzz JavaScript code layers due to two major challenges: Generating syntactically and and effectively find bugs in these binding layers. semantically correct test cases and reducing the size of the input Even without considering the binding layers, it is difficult space for fuzzing. to effectively fuzz JavaScript engines in the first place. Re- In this paper, we propose Favocado, a novel fuzzing approach searchers found that for fuzzing JavaScript engines, the quality that focuses on fuzzing binding layers of JavaScript runtime of the initial fuzzing input (i.e., seeds) greatly impacts the systems. Favocado can generate syntactically and semantically fuzzing performance [44]. This is because JavaScript engines correct JavaScript test cases through the use of extracted semantic do not directly consume the user-provided JavaScript code. information and careful maintaining of execution states. This These engines will parse user input into an abstract syntax tree way, test cases that Favocado generates do not raise unintended (AST) and then process the tree. User inputs that cannot be runtime exceptions, which substantially increases the chance of triggering binding code. Additionally, exploiting a unique fea- transformed into an AST are easily rejected. Hence, JavaScript ture (relative isolation) of binding layers, Favocado significantly test cases generated by fuzzers that are unaware of JavaScript reduces the size of the fuzzing input space by splitting DOM specifications are likely to be malformed and rejected before objects into equivalence classes and focusing fuzzing within each being processed. equivalence class. We demonstrate the effectiveness of Favocado in our experiments and show that Favocado outperforms a state- To generate syntactically correct JavaScript code as test of-the-art DOM fuzzer. Finally, during the evaluation, we find 61 cases, modern JavaScript engine fuzzers use context-free gram- previously unknown bugs in four JavaScript runtime systems mars [8, 24, 29, 37, 57] or existing semantically correct test (Adobe Acrobat Reader, Foxit PDF Reader, Chromium, and cases [27, 40, 55, 56]. However, only being syntactically correct WebKit). 33 of these bugs are security vulnerabilities. is not enough for JavaScript engines to process a test case, as many JavaScript statements have interdependent relationships. Failing to capture such relationships will lead to generating I. INTRODUCTION semantically incorrect code that raises runtime exceptions The use of JavaScript has expanded beyond web browsers when being processed. While no JavaScript fuzzers generate into the entire computing ecosystem as a general-purpose pro- fully semantically correct code as test cases, some fuzzers can gramming language. As a result, JavaScript engines are embed- generate test cases in a semantic-aware manner [27, 40, 56]. ded in a variety of commercial software (e.g., Adobe Acrobat However, the percentage of rejected test cases that are gen- and Node.js). JavaScript engines often provide important func- erated by these semantic-aware fuzzers is still a significant tionality through a binding layer, which is usually implemented problem. in unsafe languages such as C and C++. While the JavaScript Unfortunately, existing fuzzers are likely to have a difficult engines are being heavily studied, fuzzed, and hardened, their time generating test cases that can adequately fuzz JavaScript binding layers are frequently overlooked. This is exemplified binding layers. As shown in Listing 1, a typical JavaScript test case that triggers the execution of binding code once involves at least two steps: (1) Creating the object and (2) setting a Network and Distributed Systems Security (NDSS) Symposium 2021 property of the object or calling a function of the object. 21-24 February 2021 ISBN 1-891562-66-5 Due to the excessive number of JavaScript exceptions that https://dx.doi.org/10.14722/ndss.2021.23xxx randomly generated test cases raise, it is practically impossible www.ndss-symposium.org for existing fuzzers to generate legitimate JavaScript code that 1 var cb= this.getField("CheckBox"); (e.g., Favocado is able to generate JavaScript statements 2 cb.checkThisBox(0,true); that do not access previously deallocated objects). Listing 1: An example JavaScript test case that triggers the Reducing the size of the input space. Favocado excavates execution of binding code to check a checkbox. relations between binding objects from the collected se- mantic information. Then it separates all binding objects into multiple equivalence classes based on their relations. Finally, Favocado focuses on fuzzing JavaScript binding covers both steps. Not to mention, generating a sequence of layer by each equivalence class. such snippets to execute binding code multiple times. To demonstrate the generality and effectiveness of Favocado, Another challenge for effectively fuzzing the binding layer we thoroughly evaluate our prototype with different types of is the enormous input space. There are many object types that binding objects (PDF, Mojo, and DOM). These binding objects are accessible with JavaScript through the binding layer as a are implemented in four different JavaScript runtime systems Document Object Model (DOM) (e.g., in Chromium, there are (Adobe Acrobat Reader, Foxit PDF Reader, Chromium, and more than 1,000 DOM binding objects). Each DOM object WebKit). During our evaluation, Favocado finds 61 previously may have a multitude of methods and properties, some of unknown bugs, which includes 33 severe security vulnerabili- which may require hard-to-satisfy arguments such as other ties. Our evaluation results show the effectiveness of Favocado, DOM objects. Creating all objects to enumerate all properties which outperforms the state-of-the-art DOM fuzzer, Domato. and manipulate all methods is simply infeasible. An effective fuzzer that adequately fuzzes JavaScript binding code should Contributions. This paper makes the following contributions: be aware of the unique features of this layer when generating test cases. With this embedded awareness built in, a fuzzer can • We propose Favocado, a novel approach for fuzzing optimize test case generation by reducing the size of the input binding layers of JavaScript engines. Favocado generates space. semantically correct JavaScript test cases based on ex- tracted semantic information and tracking states mutation. One unique feature of the JavaScript binding layer is the Favocado also reduces the input space by being aware of relative isolation of different DOM objects. Intuitively, differ- relations between DOM objects. ent DOM objects (e.g., for Adobe Acrobat, spell.check() • We implement a prototype of Favocado and thoroughly in its spell module and Net.HTTP.request() in its evaluate it against real-world binding code in four differ- Net.HTTP module) in the binding layer are implemented ent JavaScript runtime systems (Adobe Acrobat Reader, as separate native modules, unless an object defined in Foxit PDF Reader, Chromium, and WebKit) to demon- one module can be used by code in another module. A strate the effectiveness of Favocado. We also compare JavaScript test case that calls spell.check() before Favocado against Domato and show that Favocado out- Net.HTTP.request() is essentially equivalent to another performs Domato. test case that calls the two methods in reverse order. We may • We responsibly analyzed and disclosed all bugs found by define a DOM objects relation where an object can use another Favocado that include 33 security vulnerabilities. By the object as a value to its properties or a parameter to its methods. time of writing, 13 bugs have been assigned CVE entries Based on the relations between DOM objects, we may divide during the responsible disclosure process. the entire input space into equivalence classes. In our ex- ample, spell.check() and Net.HTTP.request() will To foster further research, we open source the prototype of fall into different equivalence classes. Object-relation-aware Favocado that we developed as part of our research. The fuzzers may only mutate DOM objects within each equivalence repository is at https://github:com/favocado/Favocado.
Load more

Recommended publications
  • A Review of Fuzzing Tools and Methods 1 Introduction
    A Review of Fuzzing Tools and Methods James Fell, [email protected] Originally published in PenTest Magazine on 10th March 2017 1 Introduction Identifying vulnerabilities in software has long been an important research problem in the field of information security. Over the last decade, improvements have been made to programming languages, compilers and software engineering methods aimed at reducing the number of vulnerabilities in software [26]. In addition, exploit mitigation features such as Data Execution Prevention (DEP) [65] and Address Space Layout Randomisation (ASLR) [66] have been added to operating systems aimed at making it more difficult to exploit the vulnerabilities that do exist. Nevertheless, it is fair to say that all software applications of any significant size and complexity are still likely to contain undetected vulnerabilities and it is also frequently possible for skilled attackers to bypass any defences that are implemented at the operating system level [6, 7, 12, 66]. There are many classes of vulnerabilities that occur in software [64]. Ultimately they are all caused by mistakes that are made by programmers. Some of the most common vulnerabilities in binaries are stack based and heap based buffer overflows, integer overflows, format string bugs, off-by-one vulnerabilities, double free and use-after-free bugs [5]. These can all lead to an attacker hijacking the path of execution and causing his own arbitrary code to be executed by the victim. In the case of software running with elevated privileges this can lead to the complete compromise of the host system on which it is running.
    [Show full text]
  • Software Vulnerabilities Principles, Exploitability, Detection and Mitigation
    Software vulnerabilities principles, exploitability, detection and mitigation Laurent Mounier and Marie-Laure Potet Verimag/Université Grenoble Alpes GDR Sécurité – Cyber in Saclay (Winter School in CyberSecurity) February 2021 Software vulnerabilities . are everywhere . and keep going . 2 / 35 Outline Software vulnerabilities (what & why ?) Programming languages (security) issues Exploiting a sofwtare vulnerability Software vulnerabilities mitigation Conclusion Example 1: password authentication Is this code “secure” ? boolean verify (char[] input, char[] passwd , byte len) { // No more than triesLeft attempts if (triesLeft < 0) return false ; // no authentication // Main comparison for (short i=0; i <= len; i++) if (input[i] != passwd[i]) { triesLeft-- ; return false ; // no authentication } // Comparison is successful triesLeft = maxTries ; return true ; // authentication is successful } functional property: verify(input; passwd; len) , input[0::len] = passwd[0::len] What do we want to protect ? Against what ? I confidentiality of passwd, information leakage ? I control-flow integrity of the code I no unexpected runtime behaviour, etc. 3 / 35 Example 2: make ‘python -c ’print "A"*5000’‘ run make with a long argument crash (in recent Ubuntu versions) Why do we need to bother about crashes (wrt. security) ? crash = consequence of an unexpected run-time error not trapped/foreseen by the programmer, nor by the compiler/interpreter ) some part of the execution: I may take place outside the program scope/semantics I but can be controled/exploited by an attacker (∼ “weird machine”) out of scope execution runtime error crash normal execution possibly exploitable ... security breach ! ,! may break all security properties ... from simple denial-of-service to arbitrary code execution Rk: may also happen silently (without any crash !) 4 / 35 Back to the context: computer system security what does security mean ? I a set of general security properties: CIA Confidentiality, Integrity, Availability (+ Non Repudiation + Anonymity + .
    [Show full text]
  • Intrinsic Propensity for Vulnerability in Computers? Arbitrary Code Execution in the Universal Turing Machine
    Intrinsic Propensity for Vulnerability in Computers? Arbitrary Code Execution in the Universal Turing Machine Pontus Johnson KTH Royal Institute of Technology Stockholm, Sweden [email protected] Abstract and Weyuker in [4], “Turing’s construction of a universal computer in 1936 provided reason to believe that, at least in The universal Turing machine is generally considered to be principle, an all-purpose computer would be possible, and the simplest, most abstract model of a computer. This paper was thus an anticipation of the modern digital computer.” Or, reports on the discovery of an accidental arbitrary code execu- in the words of Stephen Wolfram [16], ‘what launched the tion vulnerability in Marvin Minsky’s 1967 implementation whole computer revolution is the remarkable fact that uni- of the universal Turing machine. By submitting crafted data, versal systems with fixed underlying rules can be built that the machine may be coerced into executing user-provided can in effect perform any possible computation.” Not only code. The article presents the discovered vulnerability in de- the universality, but also the simplicity of the universal Tur- tail and discusses its potential implications. To the best of our ing machine has attracted interest. In 1956, Claude Shannon knowledge, an arbitrary code execution vulnerability has not explored some minimal forms of the universal Turing ma- previously been reported for such a simple system. chine [13], and posed the challenge to find even smaller such machines. That exploration has continued to this day [16]. 1 Introduction A common strategy for understanding a problem is to re- duce it to its minimal form.
    [Show full text]
  • Security Threat Intelligence Report
    Security Threat Intelligence Report December 2020 In this issue COVID-19 vaccine manufacturers and supply chain targeted RansomEXX ransomware targeting Linux systems Botnet targets Linux servers, Linux IoT devices NSA top 25 vulnerabilities exploited by Chinese APT groups VMware zero-day vulnerability exploited in the wild Security Threat Intelligence Report About this report Message from Mark Hughes Fusing a range of public and proprietary information feeds, Cyber criminals are opportunists, and including DXC’s global network with COVID-19 vaccines shipping in of security operations centers and cyber intelligence services, multiple countries, attackers are targeting this report delivers an overview manufacturers and their supply chains in an of major incidents, insights into effort to monetize ransomware attacks at key trends and strategic threat awareness. the worst possible time and steal intellectual property and patient data. This month’s report also documents This report is a part of DXC Labs | Security, which provides insights the expanding attacks against Linux, Windows, and internet of and thought leadership to the things (IoT) devices. Also, the SolarWinds hack is top of mind for security industry. everyone. This is a rapidly evolving situation, and we will share Intelligence cutoff date: more details next month. For the most up to date information, November 30, 2020 refer to CISA guidance. Mark Hughes Senior Vice President Offerings & Strategic Partners DXC Technology Table of Threat Updates contents RansomEXX ransomware targeting
    [Show full text]
  • Check Point Threat Intelligence Bulletin
    November 2-8, 2020 YOUR CHECK POINT THREAT INTELLIGENCE REPORT TOP ATTACKS AND BREACHES Check Point Research has alerted against a wave of ransomware attacks targeting Israeli companies and corporations, using known ransomware families such as REvil and Ryuk, as well as a new family called ‘Pay2Key’. The ransomware is capable of rapid lateral movement within the company network. Check Point SandBlast Agent provides protection against these threats (Ransomware.Win32.Pay2Key; Ransomware.Win32.REvil) Luxottica, the world's largest eyewear company, has admitted it has been breached. The giant’s appointment scheduling application has been hacked, leading to the exposure of protected health information (PHI) for patients of eye care practices such as LensCrafters, Target Optical and EyeMed. Japanese game developer Capcom has suffered a breach leading to the shutdown of some its systems, possibly by the Ragnar Locker ransomware. Attackers claim that 1TB of sensitive data has been stolen. Check Point SandBlast Agent provides protection against this threat (Ransomware.Win32.Ragnar) The Italian liquor company Campari Group has been hit by the Ragnar Locker ransomware, leading to the theft of 2TB of unencrypted files. The attackers are demanding a $15 million ransom to retrieve the files. Check Point Research has uncovered an attack operation targeting the Sangoma and Asterisk VoIP phone systems at nearly 1,200 organizations. The attackers, most likely located in Gaza and the West Bank, target SIP servers to execute telecom fraud, sell phone number and gain access to the organizations’ VoIP servers. Check Point IPS provides protection against this threat (SIPVicious Security Scanner; Sangoma FreePBX Authentication Bypass (CVE- 2019-19006); Command Injection Over HTTP) North Korean surveillance campaign targeting the aerospace and defense sectors in Australia, Israel, Russia and India is spreading a new spyware called Torisma via fake job offers sent through social media.
    [Show full text]
  • Conti Ransomware: Evasive by Nature and How It Works
    BRAINTRACE THREAT ADVISORY REPORT APRIL 15, 2021 TABLE OF CONTENTS BACKGROUND ..................................................................................................................................................... 2 VULNERABILITIES PATCHED IN NETTLE'S SIGNATURE VERIFICATION ........................................................ 2 APPLE MAIL ZERO-CLICK VULNERABILITY ...................................................................................................... 2 FAKE NETFLIX APP CALLED FLIXONLINE LURING ANDROID USERS THROUGH WHATSAPP MESSAGES 3 CHARMING KITTEN APT GROUP TARGETING MEDICAL RESEARCHERS ...................................................... 4 GIGASET ANDROID UPDATE SERVER HACKED TO INSTALL MALWARE ON USERS' DEVICES .................. 5 'MORE_EGGS' MALWARE TARGETS PROFESSIONALS WITH LINKEDIN JOB OFFERS ................................ 6 SONICWALL EMAIL SECURITY VULNERABLE TO MALICIOUS HTTP REQUESTS .......................................... 7 CONTI RANSOMWARE: EVASIVE BY NATURE AND HOW IT WORKS. ......................................................... 8 REVIL RANSOMWARE NOW CHANGES PASSWORD TO AUTO-LOGIN IN SAFE MODE .............................. 9 NEW VULNERABILITY TARGETS POPULAR WINDOWS TIME SYNCH SOFTWARE ...................................... 9 RISING TIDE IN FIRMWARE CYBERATTACKS ................................................................................................. 10 UNPATCHED VULNERABILITY FOUND IN CISCO ROUTER MANAGEMENT INTERFACE ............................. 11 CRING RANSOMWARE
    [Show full text]
  • Automated Scanning Vulnerability Report
    Automated Scanning Vulnerability Report − Classified − Automated Scanning Vulnerability Report Performed by Beyond Security's Automated Scanning Host/s Tested: 192.168.4.122 Report Generated: 05 Jun 2007 13:31 Table of Contents Introduction Host Information Executive Summary Possible Vulnerabilities What Next? Introduction We have scanned your host/s 192.168.4.122 for 4345 known security holes. This scan took place on 5 Jun 2007 13:31 and took 0 hours and 5 minutes to complete. The 'Possible Vulnerabilities' section of this report lists security holes found during the scan, sorted by risk level. Note that some of these reported vulnerabilities could be 'false alarms' since the hole is never actually exploited during the scan. Some of what we found is purely informational; It will not help an attacker to gain access, but it will give him information about the local network or hosts. These results appear in the 'Low Risk / Intelligence Gathering' section. The last section of this report ('Security Tests') lists the security tests that were performed in this scan by category of vulnerability. 1/44 Automated Scanning Vulnerability Report Executive Summary Learn more about how vulnerabilities are classified Vulnerabilities by Host and Risk Level Total IP Address High Medium Low Vulnerabilities 192.168.4.122 113 33 60 20 Vulnerabilities By Risk Level Top Vulnerabilities By Host 2/44 Automated Scanning Vulnerability Report Vulnerabilities by Service and Risk Level Service Total High Risk Medium Risk Low Risk Vulnerabilities netbios−ns (137/udp) 1 0 0 1 microsoft−ds 101 33 58 10 (445/tcp) general/tcp 8 0 1 7 ntp (123/udp) 1 0 0 1 netbios−ssn 1 0 1 0 (139/tcp) general/icmp 1 0 0 1 Top Vulnerabilities By Service Top Vulnerable Services 3/44 Automated Scanning Vulnerability Report Possible Vulnerabilities High Medium Low Risk Factor: High A Total of 33 High Risk Vulnerability/ies was/were discovered.
    [Show full text]
  • Professional Mobile Espionage Attacks: Pegasus and Beyond
    #RSAC SESSION ID: MBS-R11 Professional Mobile Espionage Attacks: Pegasus and Beyond Andrew Blaich Max Bazaliy Staff Security Researcher Staff Security Researcher Lookout Lookout @ablaich @mbazaliy Video #RSAC What just happened? 3 #RSAC What just happened? “Lawful Intercept” 4 #RSAC The Target: Ahmed Mansoor 5 #RSAC Collaboration 6 #RSAC Citizen Lab: Pegasus Attribution C2 Infrastructure sms.webadv.co <-> mail1.nsogroup.com, nsoqa.com Linked to other targeted attacks in Mexico, Kenya Code identifiers Internal variables and function names Sophistication of software HackingTeam leak: marketing literature 7 #RSAC Pegasus Overview #RSAC What is Pegasus? Pegasus is espionage software Relies on jailbreaking a device to install itself The jailbreak is achieved via an exploit chain named Trident Pegasus can listen to all audio, video, text, and data communications coming into or leaving a phone 9 #RSAC Historical analysis Pegasus featured a non-public persistent remote jailbreak No/Minimal user interaction required 2011 public jailbreak “jailbreakme 3” is most similar December 2016 Luca Tedesco released a “jailbreakme” using Trident and Pangu. 10 #RSAC How does Pegasus operate on iOS? Stage 1 Stage 2 Stage 3 WebKit XNU Surveillance Spear-phish RCE exploitation + persistence Single use Safari UAF Kernel info leak + Re-jailbreak on CVE-2016-4657 CVE-2016-4655 reboot + Kernel UAF + Init. app hooks CVE-2016-4656 + Sync with C&C server = Jailbreak 11 #RSAC Exploit Chain - Trident CVE-2016-4657: Visiting a maliciously crafted website may lead to arbitrary
    [Show full text]
  • The Security Architecture of the Chromium Browser
    The Security Architecture of the Chromium Browser Adam Barth∗ Collin Jackson∗ UC Berkeley Stanford University Charles Reis∗ Google Chrome Team University of Washington Google Inc. ABSTRACT There have been a number of research proposals for mod- Most current web browsers employ a monolithic architec- ular browser architectures [8, 27, 5, 7] that contain multiple ture that combines \the user" and \the web" into a single protection domains. Like Chromium's architecture, these protection domain. An attacker who exploits an arbitrary proposals aim to provide security against an attacker who code execution vulnerability in such a browser can steal sen- can exploit an unpatched vulnerability. Unlike Chromium's sitive files or install malware. In this paper, we present the architecture, these proposals trade off compatibility with ex- security architecture of Chromium, the open-source browser isting web sites to provide architectural isolation between upon which Google Chrome is built. Chromium has two web sites or even individual pages. The browser's secu- modules in separate protection domains: a browser kernel, rity policy, known as the \same-origin policy," is complex which interacts with the operating system, and a rendering and can make such fine-grained isolation difficult to achieve engine, which runs with restricted privileges in a sandbox. without disrupting existing sites. Users, however, demand This architecture helps mitigate high-severity attacks with- compatibility because a web browser is only as useful as the out sacrificing compatibility with existing web sites. We sites that it can render. To be successful, a modular browser define a threat model for browser exploits and evaluate how architecture must support the entire web platform in addi- the architecture would have mitigated past vulnerabilities.
    [Show full text]
  • Hotfuzz: Discovering Algorithmic Denial-Of-Service Vulnerabilities Through Guided Micro-Fuzzing
    HotFuzz: Discovering Algorithmic Denial-of-Service Vulnerabilities Through Guided Micro-Fuzzing William Blairy, Andrea Mambretti∗, Sajjad Arshadz, Michael Weissbacher∗, William Robertson∗, Engin Kirda∗, and Manuel Egeley yBoston University ∗zNortheastern University yfwdblair, [email protected], ∗fmbr, mw, wkr, [email protected], [email protected] Abstract—Fifteen billion devices run Java and many of them are being released to unauthorized principals (confidentiality vio- connected to the Internet. As this ecosystem continues to grow, lations). The third traditional security property, availability, is it remains an important task to discover any unknown security not exempt from this issue. However, denial-of-service (DoS) threats these devices face. Fuzz testing repeatedly runs software as a vulnerability class tends to be viewed as simplistic, noisy, on random inputs in order to trigger unexpected program and easy (in principle) to defend against. behaviors, such as crashes or timeouts, and has historically re- vealed serious security vulnerabilities. Contemporary fuzz testing This view, however, is simplistic, as availability vulnerabilities techniques focus on identifying memory corruption vulnerabilities and exploits against them can take sophisticated forms. Algo- that allow adversaries to achieve either remote code execution or rithmic Complexity (AC) vulnerabilities are one such form, information disclosure. Meanwhile, Algorithmic Complexity (AC) where a small adversarial input induces worst-case1 behavior vulnerabilities, which are a common attack vector for denial-of- in the processing of that input, resulting in a denial of service. service attacks, remain an understudied threat. While in the textbook example against a hash table an adver- In this paper, we present HotFuzz, a framework for automatically sary inserts values with colliding keys to degrade the complex- discovering AC vulnerabilities in Java libraries.
    [Show full text]
  • Softether VPN Server NDIS 5.X Windows Local Bridge Driver Local Privilege Escalation Vulnerability
    2019/07/09: SE201901: SoftEther VPN Server NDIS 5.x Windows Local Bridge Driver Local Privilege Escalation Vulnerability Published: 2019/07/09 Related: CVE-2019-11868 SoftEther VPN Security Advisory articles are published for high impact vulnerabilities (an arbitrary code execution or equivalent). Summary A vulnerability in the NDIS 5.x based Local Bridge module for SoftEther VPN 4.29 Build 9680 or older could allow the local Windows-logged-on attacker (who is already logged on to the same computer which run VPN servers) to realize a Windows local authenticated privilege escalation attacks or could result in BSODs. To exploit this vulnerability, an attacker must log on to the local Windows system which is the same computer which running the SoftEther VPN Server. An attacker could then run a specially crafted program that could exploit the vulnerability. This vulnerability affects only when the server computer is running the Local Bridge function or the SecureNAT function on Windows 2000, Windows XP, Windows Vista, Windows 7 and Windows 8.0 (not Windows 8.1). Same Windows Server family of these Windows versions could also be affected. Any systems with Windows 8.1 or Windows 10 (includes Windows Server 2012 R2, 2016, 2019), or Linux, FreeBSD, macOS or Solaris are not to be affected. This vulnerability affects only when: 1. A VPN system administrator shares a single Windows computer between the VPN server feature and local or remote login terminals for unprivileged users. (e.g. Terminal Service for the organization) or 2. A VPN system administrator allows attackers to execute any untrusted arbitrary programs in the local VPN server computer.
    [Show full text]
  • Foxes Among Us
    Foxes Among Us Foxit Reader Vulnerability Discovery and Exploitation Steven Seeley (mr_me) of Source Incite # whoami • Independent Security Researcher • ZDI platinum researcher for 2017, 2018 and 2019 • Sharing n-day writeup’s & exploit’s @ srcincite.io • Enjoys body building and practicing CRCA Wing Chun Kung Fu in México • Forever trying to learn Spanish! • ¡Me encanta México! Why target Foxit Reader? • PDF is a huge attack surface • Image rendering • JavaScript • Stream decoding • Foxit is taking vulnerability reports seriously • High user-base, the first alternative to Adobe Reader • Last public exploit was in 2010 - Affecting version 4.1.1 Why target Foxit Reader? ZERODIUM is currently acquiring zero-day exploits affecting the following products: Vulnerability != Exploit Platform and Target • Foxit Reader v9.0.1.1049 • FoxitReader.exe - SHA1: a01a5bde0699abda8294d73544a1ec6b4115fa68 • Latest version is 9.1.0.5096 • Windows 7 x86 v6.1.7601 (Fully patched) • Does/Will this work on Windows 10? • Probably, haven’t tested Agenda • Introduction to the bug classes 1. Typed Array Uninitialized Pointer Information Disclosure (CVE-2018-9948) • Vulnerability Discovery • Custom developed tools • Demo: JavaScript Bridge • Vulnerability Exploitation • Finding a suitable object • Leaking the vtable and calculating the base of FoxitReader Agenda 2. Text Annotations point Use-After-Free Remote Code Execution (CVE-2018-9958) • Vulnerability Discovery • Grammar based fuzzing • Vulnerability Exploitation • Heap Spray Leaking a TypedArray • Replacing the freed object • The ROP chain • Demo: Foxit Exploit • Conclusion What is an Uninitialized Pointer Vulnerability? Example: Foo *bar; bar->search('test'); The bar variable hasn’t been initialized yet, meaning it can contain data from a previous allocation. This can result in arbitrary execution of code via a vtable dispatch.
    [Show full text]