Security readout for executives and security teams
Plain-English summary
This flaw can let an attacker plant a normal browser cookie that a vulnerable PHP application may mistakenly trust as a stronger __Host- or __Secure- cookie. The main business risk is integrity loss in applications that use those cookie prefixes for security decisions, especially authentication or session controls.
Executive priority
Treat this as a near-term patching item for PHP-backed web systems, not an emergency absent exploitation evidence. Prioritize customer-facing or authentication-sensitive applications first because the documented impact is integrity compromise.
Technical view
PHP versions before 7.4.31, 8.0.24, and 8.1.11 mishandle cookie names because dot-to-underscore normalization can change how $_COOKIE entries are interpreted. The CVE states network and same-site attackers can set an insecure cookie that PHP applications treat as __Host- or __Secure-prefixed.
Likely exposure
Exposure is most likely in web applications running affected PHP 7.4.x, 8.0.x, or 8.1.x versions, including distribution-packaged PHP. Risk is higher where application logic relies on __Host- or __Secure- cookie names for trust boundaries.
Exploitation context
The provided sources do not indicate CISA KEV listing or confirmed active exploitation. CVSS marks network attack vector, low complexity, no privileges, and user interaction required, with high integrity impact and no stated confidentiality or availability impact.
Researcher notes
Focus review on PHP cookie-name normalization and application assumptions around reserved cookie prefixes. Evidence provided establishes affected versions and fixed PHP releases, but does not include product-specific exploitability, broad exploitation, or alternate mitigations beyond vendor updates.
Mitigation direction
- Upgrade PHP to 7.4.31, 8.0.24, 8.1.11, or later supported releases.
- Apply Debian, Fedora, Gentoo, NetApp, or other vendor backported security packages where applicable.
- Prioritize applications using __Host- or __Secure- cookies for authentication or authorization decisions.
- Review vendor advisories before applying product-specific workarounds or lifecycle decisions.
Validation and detection
- Inventory production, staging, containers, and base images for affected PHP branches and package versions.
- Confirm vendor package changelogs include the CVE-2022-31629 fix or equivalent backport.
- Review application code that reads $_COOKIE and trusts __Host- or __Secure- cookie names.
- Regression test cookie-based security flows after PHP or distribution package updates.
Public sources used
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-1284: 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 lookupCWE-20: 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-31629 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
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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:L/PR:N/UI:R/S:U/C:N/I:H/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://bugs.php.net/bug.php?id=81727CVE reference
- FEDORA-2022-0b77fbd9e7CVE reference · vendor-advisory
- FEDORA-2022-afdea1c747CVE reference · vendor-advisory
- FEDORA-2022-f204e1d0edCVE reference · vendor-advisory
- DSA-5277CVE reference · vendor-advisory
- GLSA-202211-03CVE reference · vendor-advisory
- https://security.netapp.com/advisory/ntap-20221209-0001/CVE reference
- [debian-lts-announce] 20221215 [SECURITY] [DLA 3243-1] php7.3 security updateCVE reference · mailing-list
- FEDORA-2024-b46619f761CVE reference · vendor-advisory
- FEDORA-2024-39d50cc975CVE reference · vendor-advisory
- FEDORA-2024-5e8ae0def0CVE reference · vendor-advisory
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZGWIK3HMBACERGB4TSBB2JUOMPYY2VKY/CVE reference
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KJZK3X6B7FBE32FETDSMRLJXTFTHKWSY/CVE reference
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.
Improper Validation of Specified Quantity in Input
Improper Validation of Specified Quantity in Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.