Security readout for executives and security teams
HTTP::Daemon before 6.15 can misunderstand malformed HTTP request bodies. In the wrong deployment, that parsing gap could let a request be interpreted differently by intermediaries and the Perl server, risking unauthorized API access or cache poisoning. The cited advisory says real-world exposure is uncertain because this library is often used for local development and testing. Exposure is most likely in Perl applications that run HTTP::Daemon below 6.15 as a reachable HTTP service. Risk is lower where it is only a local test or development dependency, or where production traffic is handled entirely by Apache, Nginx, or another server. Treat as a high-priority inventory-and-patch item, especially for internet-facing Perl services. The business urgency depends on whether HTTP::Daemon is actually in the production request path. Do not assume exposure from dependency presence alone. Mitigation focus: Upgrade HTTP::Daemon or libhttp-daemon-perl to version 6.15 or a vendor-fixed package.; Apply Debian or Fedora security updates where managed by those distributions.; If upgrade is blocked, reject abnormal Content-Length values with a 400 response..
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-444: 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-2022-31081 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
- High
- CVSS
- 7.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://portswigger.net/research/http-desync-attacks-request-smuggling-rebornCVE reference
- https://github.com/libwww-perl/HTTP-Daemon/security/advisories/GHSA-cg8c-pxmv-w7cfCVE reference
- https://github.com/libwww-perl/HTTP-Daemon/commit/8dc5269d59e2d5d9eb1647d82c449ccd880f7fd0CVE reference
- https://github.com/libwww-perl/HTTP-Daemon/commit/e84475de51d6fd7b29354a997413472a99db70b2CVE reference
- https://cwe.mitre.org/data/definitions/444.htmlCVE reference
- https://datatracker.ietf.org/doc/html/rfc7230#section-9.5CVE reference
- [debian-lts-announce] 20220930 [SECURITY] [DLA 3127-1] libhttp-daemon-perl security updateCVE reference · mailing-list
- FEDORA-2023-c230cc08c4CVE reference · vendor-advisory
- FEDORA-2023-424636c7cbCVE reference · vendor-advisory
- FEDORA-2023-748e811334CVE 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.
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
