🛡️ CVE-2022-36032 — http

🟡 CVSS 5.3 — Medium ✅ No Known Exploit CWE-20 NVD
5.3
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

ReactPHP's HTTP server parses encoded cookie names so malicious __Host- and __Secure- cookies can be sent

Impact

In ReactPHP's HTTP server component versions below v1.7.0, when ReactPHP is processing incoming HTTP cookie values, the cookie names are url-decoded. This may lead to cookies with prefixes like __Host- and __Secure- confused with cookies that decode to such prefix, thus leading to an attacker being able to forge cookie which is supposed to be secure. See also CVE-2020-7070 and CVE-2020-8184 for more information.

Patches

  • https://github.com/reactphp/http/commit/663c9a3b77b71463fa7fcb76a6676ffd16979dd6 - Fixed in [reactphp/http v1.7.0](https://github.com/reactphp/http/releases/tag/v1.7.0)

Workarounds

Infrastructure or DevOps can place a reverse proxy in front of the ReactPHP HTTP server to filter out any unexpected Cookie request headers.

References

  • CVE-2020-7070, https://bugs.php.net/bug.php?id=79699 and https://github.com/php/php-src/commit/6559fe912661ca5ce5f0eeeb591d928451428ed0
  • CVE-2020-8184, https://hackerone.com/reports/895727 and https://github.com/rack/rack/commit/1f5763de6a9fe515ff84992b343d63c88104654c
  • Originally introduced via https://github.com/reactphp/http/pull/175

Credits

  • Thanks to Marco Squarcina (TU Wien) for reporting this and working with us to coordinate this security advisory

For more information

If you have any questions or comments about this advisory:

  • [Join the discussion](https://github.com/orgs/reactphp/discussions/465)
  • Email us at [email protected]

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity low, availability none.

Weakness class

CVE-2022-36032 is classified as CWE-20: Improper Input Validation. The application accepts input without checking that it has the expected form, so malformed values reach code that assumes they are well formed.

Affected software

CVE-2022-36032 is recorded against 2 packages.

  • http (from 0.7.0 up to 1.7.0)
  • react/http (from 0.7.0 up to 1.7.0)

Timeline and source

Published on 6 September 2022 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

github.com
github.com
github.com
github.com
github.com
github.com
github.com
github.com

CVE-2022-36032 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity MEDIUM
CVSS Score 5.3
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CWE CWE-20
Public Exploit ✅ No
Source NVD
Published 2022-09-06
Updated 2026-08-12
Modified 2026-06-17

Affected Packages

Software From version Fixed in
http 0.7.0 1.7.0
react/http 0.7.0 1.7.0

References

Issue Tracking, Patch, Third Party Advisory https://github.com/reactphp/http/pull/175
Release Notes, Third Party Advisory https://github.com/reactphp/http/releases/tag/v1.7.0
Issue Tracking, Patch, Third Party Advisory https://github.com/reactphp/http/pull/175
Release Notes, Third Party Advisory https://github.com/reactphp/http/releases/tag/v1.7.0

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in http

CVE-2022-36032 is rated CVSS 5.3 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.