Security readout for executives and security teams
This Tomcat flaw can send a response, or part of one, to the wrong client under a rare concurrency condition. The business risk is unintended data disclosure from affected Tomcat-hosted applications, not system takeover. The published severity is low because triggering it is extremely difficult. Exposure is limited to Apache Tomcat 10.1.0-M1 through 10.1.0-M12, 10.0.0-M1 through 10.0.18, 9.0.0-M1 through 9.0.60, and 8.5.0 through 8.5.77. Public-facing or multi-user applications have the most relevant confidentiality concern. Treat this as a low-severity confidentiality issue. It should be remediated through normal patch cycles, faster for externally exposed or sensitive applications, but the sources do not support emergency response absent other local risk factors. Mitigation focus: Identify all Apache Tomcat instances and package-managed tomcat9 installations.; Upgrade affected Tomcat versions according to Apache vendor guidance.; Apply Debian security updates where Tomcat is installed from Debian packages..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-362: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-43980 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N2.21.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
3.7LowVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://lists.apache.org/thread/3jjqbsp6j88b198x5rmg99b1qr8ht3g3CVE reference
- [debian-lts-announce] 20221026 [SECURITY] [DLA 3160-1] tomcat9 security updateCVE reference · mailing-list
- DSA-5265CVE reference · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.