CVE-2022-32749
Published: 19 December 2022
Summary
CVE-2022-32749 is a high-severity Improper Check for Unusual or Exceptional Conditions (CWE-754) vulnerability in Apache Traffic Server. Its CVSS base score is 7.5 (High).
Operationally, ranked in the top 8.7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
Apache Traffic Server versions 8.0.0 through 9.1.3 are affected by an improper check for unusual or exceptional conditions vulnerability when handling requests, assigned CVE-2022-32749 and CWE-754. The flaw received a CVSS 3.1 score of 7.5 reflecting network attack vector, low complexity, and no required privileges or user interaction, with the sole impact being high availability loss.
An unauthenticated remote attacker can send crafted requests that trigger the condition, causing the server to crash and producing a denial-of-service outcome without any confidentiality or integrity compromise.
The Apache project published details in mailing-list announcements at the referenced thread URLs, identifying the affected range and directing users to later releases that resolve the issue.
EPSS scores have remained low and essentially flat at approximately 0.065, indicating no material post-disclosure rise in observed exploitation interest.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-35815
Vulnerability details
Improper Check for Unusual or Exceptional Conditions vulnerability handling requests in Apache Traffic Server allows an attacker to crash the server under certain conditions. This issue affects Apache Traffic Server: from 8.0.0 through 9.1.3.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Requires detection and response to audit logging failures as an unusual or exceptional condition.
Implements detection of unusual or exceptional conditions followed by safe mode entry, reducing the window for exploitation of unchecked conditions.
Training ensures users perform required checks for unusual or exceptional conditions as part of contingency roles, limiting attacker leverage from skipped validations.
IR testing directly validates checks for unusual or exceptional conditions that could indicate security incidents.
Requires ongoing monitoring of organization-defined metrics and analysis, enabling checks for unusual or exceptional conditions.
Security testing routinely checks for unusual or exceptional inputs/conditions, identifying missing validation steps that flaw remediation then resolves.
Requires detection of unusual conditions followed by a controlled transition to the defined failure state.
MTTF determination forces explicit checks for conditions that precede predictable component failure.