{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-53007 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-53007 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-53007 is a high-severity vulnerability in espressif arduino-esp32, published on 26 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-53007 and fix it if it is affected.\n\nWhat it is: CVE-2025-53007 is a high-severity vulnerability in espressif arduino-esp32, published on 26 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-53007 in the wild and no public exploit code.\n\nAffected product: espressif arduino-esp32. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-53007/ (Markdown: https://insights.sbomify.com/CVE-2025-53007/index.md)","id":"CVE-2025-53007","markdown":"https://insights.sbomify.com/CVE-2025-53007/index.md","name":"CVE-2025-53007","record":{"aliases":["GHSA-5476-9jjq-563m"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"ESP32 Arduino core","requires_auth":"none","summary":"Attackers can inject CRLF characters into HTTP headers via the sendHeader function, enabling HTTP response splitting and header manipulation in ESP32 applications.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.9,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-113","name":"Improper Neutralization of CRLF Sequences in HTTP Headers"}],"description":"arduino-esp32 provides an Arduino core for the ESP32. Versions prior to 3.3.0-RC1 and 3.2.1 contain a HTTP Response Splitting vulnerability. The `sendHeader` function takes arbitrary input for the HTTP header name and value, concatenates them into an HTTP header line, and appends this to the outgoing HTTP response headers. There is no validation or sanitization of the `name` or `value` parameters before they are included in the HTTP response. If an attacker can control the input to `sendHeader` (either directly or indirectly), they could inject carriage return (`\\r`) or line feed (`\\n`) characters into either the header name or value. This could allow the attacker to inject additional headers, manipulate the structure of the HTTP response, potentially inject an entire new HTTP response (HTTP Response Splitting), and/or ause header confusion or other HTTP protocol attacks. Versions 3.3.0-RC1 and 3.2.1 contain a fix for the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"arduino-esp32 vulnerable to CRLF injection in WebServer.cpp","id":"CVE-2025-53007","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"GLPI's MailCollector Receiver is vulnerable to credential exfiltration","id":"CVE-2025-53008"},"packages":[],"prev":{"headline":"Dataease PostgreSQL \u0026 Redshift Data Source JDBC Connection Parameters Bypass Vulnerability","id":"CVE-2025-53006"},"products":["arduino-esp32"],"published":"2025-06-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-27","vendors":["espressif"]},"summary":"Attackers can inject CRLF characters into HTTP headers via the sendHeader function, enabling HTTP response splitting and header manipulation in ESP32 applications.","url":"https://insights.sbomify.com/CVE-2025-53007/"}