ID CVE-2015-2080
Summary The exception handling code in Eclipse Jetty before 9.2.9.v20150224 allows remote attackers to obtain sensitive information from process memory via illegal characters in an HTTP header, aka JetLeak.
References
Vulnerable Configurations
  • Fedora 22
    cpe:2.3:o:fedoraproject:fedora:22
  • Eclipse Jetty 9.2.3
    cpe:2.3:a:eclipse:jetty:9.2.3
  • Eclipse Jetty 9.2.4
    cpe:2.3:a:eclipse:jetty:9.2.4
  • Eclipse Jetty 9.2.5
    cpe:2.3:a:eclipse:jetty:9.2.5
  • Eclipse Jetty 9.2.6
    cpe:2.3:a:eclipse:jetty:9.2.6
  • Eclipse Jetty 9.2.7
    cpe:2.3:a:eclipse:jetty:9.2.7
  • Eclipse Jetty 9.2.8
    cpe:2.3:a:eclipse:jetty:9.2.8
  • cpe:2.3:a:eclipse:jetty:9.3.0:m0
    cpe:2.3:a:eclipse:jetty:9.3.0:m0
  • cpe:2.3:a:eclipse:jetty:9.3.0:m1
    cpe:2.3:a:eclipse:jetty:9.3.0:m1
CVSS
Base: 5.0 (as of 14-10-2016 - 12:41)
Impact:
Exploitability:
CWE CWE-200
CAPEC
  • Subverting Environment Variable Values
    The attacker directly or indirectly modifies environment variables used by or controlling the target software. The attacker's goal is to cause the target software to deviate from its expected operation in a manner that benefits the attacker.
  • Footprinting
    An attacker engages in probing and exploration activity to identify constituents and properties of the target. Footprinting is a general term to describe a variety of information gathering techniques, often used by attackers in preparation for some attack. It consists of using tools to learn as much as possible about the composition, configuration, and security mechanisms of the targeted application, system or network. Information that might be collected during a footprinting effort could include open ports, applications and their versions, network topology, and similar information. While footprinting is not intended to be damaging (although certain activities, such as network scans, can sometimes cause disruptions to vulnerable applications inadvertently) it may often pave the way for more damaging attacks.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Browser Fingerprinting
    An attacker carefully crafts small snippets of Java Script to efficiently detect the type of browser the potential victim is using. Many web-based attacks need prior knowledge of the web browser including the version of browser to ensure successful exploitation of a vulnerability. Having this knowledge allows an attacker to target the victim with attacks that specifically exploit known or zero day weaknesses in the type and version of the browser used by the victim. Automating this process via Java Script as a part of the same delivery system used to exploit the browser is considered more efficient as the attacker can supply a browser fingerprinting method and integrate it with exploit code, all contained in Java Script and in response to the same web page request by the browser.
  • Session Credential Falsification through Prediction
    This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
  • Reusing Session IDs (aka Session Replay)
    This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.
  • Using Slashes in Alternate Encoding
    This attack targets the encoding of the Slash characters. An attacker would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the attacker many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL NONE NONE
nessus via4
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2015-2673.NASL
    description Rebase to upstream version 9.2.9, resolves CVE-2015-2080 security vulnerability. Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-01-16
    modified 2016-10-18
    plugin id 81841
    published 2015-03-17
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=81841
    title Fedora 22 : jetty-9.2.9-1.fc22 (2015-2673)
  • NASL family Web Servers
    NASL id JETTY_CVE-2015-2080.NASL
    description The remote instance of Jetty is affected by a remote memory disclosure vulnerability in the HttpParser module due to incorrect handling of illegal characters in header values. When an illegal character is encountered in an HTTP request, Jetty writes a response in a shared buffer that was used in a previous request. Jetty's response to the client includes this shared buffer which contains potentially sensitive data from the previous request. An attacker, using specially crafted requests containing variable length strings of illegal characters, can steal sensitive header data (e.g. cookies, authentication tokens) or sensitive POST data (e.g. credentials).
    last seen 2019-01-16
    modified 2018-11-15
    plugin id 81576
    published 2015-02-27
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=81576
    title Jetty HttpParser Error Remote Memory Disclosure
packetstorm via4
refmap via4
bid 72768
bugtraq 20150225 GDS Labs Alert [CVE-2015-2080] - JetLeak Vulnerability: Remote Leakage Of Shared Buffers In Jetty Web Server
confirm https://github.com/eclipse/jetty.project/blob/jetty-9.2.x/advisories/2015-02-24-httpparser-error-buffer-bleed.md
fedora FEDORA-2015-2673
fulldisc 20150301 GDS Labs Alert [CVE-2015-2080] - JetLeak Vulnerability: Remote Leakage Of Shared Buffers In Jetty Web Server
misc
mlist
  • [jetty-announce] 20150224 Critical Security Release of Jetty 9.2.9.v20150224
  • [jetty-announce] 20150225 CVE-2015-2080 : JetLeak Vulnerability Remote Leakage of Shared Buffers in Jetty
sectrack 1031800
Last major update 17-10-2016 - 14:35
Published 07-10-2016 - 10:59
Last modified 09-10-2018 - 15:56
Back to Top