CVE-2016-8745

Assigned byThe organization (CNA) that assigned this CVE ID and published the record, usually the vendor.
Apache Software Foundation (opens in new tab)
Published
Last modified
NVD status
Modified
CVSS 3.07.5High

Description

A bug in the error handling of the send file code for the NIO HTTP connector in Apache Tomcat 9.0.0.M1 to 9.0.0.M13, 8.5.0 to 8.5.8, 8.0.0.RC1 to 8.0.39, 7.0.0 to 7.0.73 and 6.0.16 to 6.0.48 resulted in the current Processor object being added to the Processor cache multiple times. This in turn meant that the same Processor could be used for concurrent requests. Sharing a Processor can result in information leakage between requests including, not not limited to, session ID and the response body. The bug was first noticed in 8.5.x onwards where it appears the refactoring of the Connector code for 8.5.x onwards made it more likely that the bug was observed. Initially it was thought that the 8.5.x refactoring introduced the bug but further investigation has shown that the bug is present in all currently supported Tomcat versions.

Exploitation

Whether attackers are exploiting this vulnerability, and how likely they are to try in the next 30 days.

CISA SSVC assessmentAbout SSVC (opens in new tab)

CISA's assessment of whether it's exploited, whether attacks can be automated and how much control an attacker gains.

ExploitationWhether CISA has seen exploit code or attacks for this vulnerability.
None known
AutomatableWhether attackers can exploit it at scale without manual steps.
Yes
Technical impactHow much control of the affected system an attacker gains.
Partial control
Assessed

FIRST Exploit Prediction Scoring System (EPSS)About EPSS (opens in new tab)

FIRST's estimate of the chance attackers try to exploit this vulnerability in the next 30 days.

Probability of exploitationIt predicts attempts, not success, and is updated daily.
16.038%
Compared with other CVEs
At or above 96.981% of scored CVEs
Scored

Affected products

The products and versions with the vulnerability.

Listed by CNA

The products and versions affected, according to the organization that published this CVE.

VendorProductAffected versions
Apache Software FoundationApache Tomcat
  • 9.0.0.M1 to 9.0.0.M13
  • 8.5.0 to 8.5.8
  • 8.0.0.RC1 to 8.0.39
  • 7.0.0 to 7.0.73
  • 6.0.16 to 6.0.48

Listed by NVD

The CPE names vulnerability scanners match, including products that bundle the affected software.

VendorProductTypeVulnerable versions
apachetomcatApplication
  • 7.0.0
  • 7.0.1
  • 7.0.2
  • 7.0.3
  • 7.0.4
  • 7.0.5
  • 7.0.6
  • 7.0.7
  • 7.0.8
  • 7.0.9
  • 7.0.11
  • 7.0.12
  • 7.0.13
  • 7.0.14
  • 7.0.15
  • 7.0.16
  • 7.0.17
  • 7.0.18
  • 7.0.19
  • 7.0.20
  • 7.0.21
  • 7.0.22
  • 7.0.23
  • 7.0.24
  • 7.0.25
  • 7.0.26
  • 7.0.27
  • 7.0.28
  • 7.0.29
  • 7.0.30
  • 7.0.31
  • 7.0.32
  • 7.0.33
  • 7.0.34
  • 7.0.35
  • 7.0.36
  • 7.0.37
  • 7.0.38
  • 7.0.39
  • 7.0.40
  • 7.0.41
  • 7.0.42
  • 7.0.43
  • 7.0.44
  • 7.0.45
  • 7.0.46
  • 7.0.47
  • 7.0.48
  • 7.0.49
  • 7.0.50
  • 7.0.52
  • 7.0.53
  • 7.0.54
  • 7.0.55
  • 7.0.56
  • 7.0.57
  • 7.0.58
  • 7.0.59
  • 7.0.60
  • 7.0.61
  • 7.0.62
  • 7.0.63
  • 7.0.64
  • 7.0.65
  • 7.0.66
  • 7.0.67
  • 7.0.68
  • 7.0.69
  • 7.0.70
  • 7.0.71
  • 7.0.72
  • 7.0.73
  • 8.0
  • 8.0.0
  • 8.0.1
  • 8.0.2
  • 8.0.3
  • 8.0.4
  • 8.0.5
  • 8.0.6
  • 8.0.7
  • 8.0.8
  • 8.0.9
  • 8.0.10
  • 8.0.11
  • 8.0.12
  • 8.0.13
  • 8.0.14
  • 8.0.15
  • 8.0.16
  • 8.0.17
  • 8.0.18
  • 8.0.19
  • 8.0.20
  • 8.0.21
  • 8.0.22
  • 8.0.23
  • 8.0.24
  • 8.0.25
  • 8.0.26
  • 8.0.27
  • 8.0.28
  • 8.0.29
  • 8.0.30
  • 8.0.31
  • 8.0.32
  • 8.0.33
  • 8.0.34
  • 8.0.35
  • 8.0.36
  • 8.0.37
  • 8.0.38
  • 8.0.39
  • 8.5.0
  • 8.5.1
  • 8.5.2
  • 8.5.3
  • 8.5.4
  • 8.5.5
  • 8.5.6
  • 8.5.7
  • 8.5.8
  • 9.0.0

Severity

How serious the vulnerability is if exploited, scored from 0 to 10 with the CVSS standard (opens in new tab).

  • 7.5 HighCVSS 3.0 · PrimaryPrimary scores are NVD's own. Secondary scores come from the organization that published the CVE, or from CISA. · Scored by NVD (opens in new tab)
    Attack vectorWhere the attacker has to be. Network is the widest: anywhere on the Internet.
    Network
    Attack complexityWhether the attack depends on conditions the attacker doesn't control.
    Low
    Privileges requiredThe access the attacker needs before attacking.
    None
    User interactionWhether someone other than the attacker has to do something, like open a link.
    None
    ScopeWhether the attack can reach beyond the vulnerable component.
    Unchanged
    ConfidentialityHow much data the attacker can read.
    High
    IntegrityHow much data the attacker can change.
    None
    AvailabilityHow much the attacker can disrupt the system or service.
    None

    CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NView in FIRST's calculator (opens in new tab)

  • 5 MediumCVSS 2.0 · PrimaryPrimary scores are NVD's own. Secondary scores come from the organization that published the CVE, or from CISA. · Scored by NVD (opens in new tab)
    Attack vectorWhere the attacker has to be. Network is the widest: anywhere on the Internet.
    Network
    Attack complexityWhether the attack depends on conditions the attacker doesn't control.
    Low
    AuthenticationHow many times the attacker has to sign in.
    None
    ConfidentialityHow much data the attacker can read.
    Partial
    IntegrityHow much data the attacker can change.
    None
    AvailabilityHow much the attacker can disrupt the system or service.
    None

    AV:N/AC:L/Au:N/C:P/I:N/A:NView in NVD's calculator (opens in new tab)

Weaknesses and attack patterns

The type of bug behind the vulnerability, and how attackers exploit that type.

  • 7PK - Errors · CWE-388 (opens in new tab)

    This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that occur when an application does not properly handle errors that occur during processing. According to the authors of the Seven Pernicious Kingdoms, "Errors and error handling represent a class of API. Errors related to error handling are so common that they deserve a special kingdom of their own. As with 'API Abuse,' there are two ways to introduce an error-related security vulnerability: the most common one is handling errors poorly (or not at all). The second is producing errors that either give out too much information (to possible attackers) or are difficult to handle."

    Mapping guidance
    Prohibited

References

Advisories, patches, exploits and more about this vulnerability.

This product uses the NVD API but is not endorsed or certified by the NVD (opens in new tab). CVE records from the CVE List (opens in new tab), weakness types from MITRE's CWE (opens in new tab)™ and attack patterns from its CAPEC (opens in new tab)™ are © The MITRE Corporation, used under the CVE (opens in new tab), CWE (opens in new tab) and CAPEC (opens in new tab) terms of use. Known exploited vulnerabilities and SSVC assessments are from CISA. Exploit predictions are from FIRST's EPSS (opens in new tab). About this data