{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-31698 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-31698 is a high-severity missing authorization vulnerability in Apache Traffic Server, published on 19 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-31698 and fix it if it is affected.\n\nWhat it is: CVE-2025-31698 is a high-severity missing authorization vulnerability in Apache Traffic Server, published on 19 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-31698 in the wild and no public exploit code.\n\nAffected product: Apache Traffic Server. 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-31698/ (Markdown: https://insights.sbomify.com/CVE-2025-31698/index.md)","id":"CVE-2025-31698","markdown":"https://insights.sbomify.com/CVE-2025-31698/index.md","name":"CVE-2025-31698","record":{"aliases":["DEBIAN-CVE-2025-31698","GHSA-v2wx-jg5q-pj8q","UBUNTU-CVE-2025-31698"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Apache Traffic Server","requires_auth":"none","summary":"Attackers can bypass IP-based access controls in Apache Traffic Server when PROXY protocol is enabled, allowing unauthorized access to protected resources.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"traffic_server","vendor":"apache"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"ACL configured in ip_allow.config or remap.config does not use IP addresses that are provided by PROXY protocol.\n\nUsers can use a new setting (proxy.config.acl.subjects) to choose which IP addresses to use for the ACL if Apache Traffic Server is configured to accept PROXY protocol. \nThis issue affects undefined: from 10.0.0 through 10.0.6, from 9.0.0 through 9.2.10.\n\nUsers are recommended to upgrade to version 9.2.11 or 10.0.6, which fixes 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":true,"headline":"Apache Traffic Server: Client IP address from PROXY protocol is not used for ACL","id":"CVE-2025-31698","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"apache:traffic_server","products":["apache:traffic_server"],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Apache Traffic Server: Origin connection still owed a request body is reused, enabling request smuggling","id":"CVE-2025-31699"},"packages":[],"prev":{"headline":"Formatter Suite - Moderately critical - Cross site scripting - SA-CONTRIB-2025-026","id":"CVE-2025-31697"},"products":["Apache Traffic Server"],"published":"2025-06-19","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2014-3525","kev_date_added":null,"published":"2014-08-22"},{"cvss_score":9.8,"headline":"heap-buffer-overflow with stats-over-http plugin","id":"CVE-2021-43082","kev_date_added":null,"published":"2021-11-03"},{"cvss_score":9.8,"headline":"Dynamic stack buffer overflow in cachekey plugin","id":"CVE-2021-35474","kev_date_added":null,"published":"2021-06-30"},{"cvss_score":9.8,"headline":"Other in Apache Traffic Server","id":"CVE-2019-17559","kev_date_added":null,"published":"2020-03-23"},{"cvss_score":9.8,"headline":"Other in Apache Traffic Server","id":"CVE-2019-17565","kev_date_added":null,"published":"2020-03-23"},{"cvss_score":9.8,"headline":"Other in Apache Traffic Server","id":"CVE-2020-1944","kev_date_added":null,"published":"2020-03-23"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2014-3624","kev_date_added":null,"published":"2017-10-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-20","vendors":["Apache Software Foundation"]},"summary":"Attackers can bypass IP-based access controls in Apache Traffic Server when PROXY protocol is enabled, allowing unauthorized access to protected resources.","url":"https://insights.sbomify.com/CVE-2025-31698/"}