{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-6839 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-6839 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-6839 is a medium-severity vulnerability in n/a, published on 7 Sep 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2016-6839 and fix it if it is affected.\n\nWhat it is: CVE-2016-6839 is a medium-severity vulnerability in n/a, published on 7 Sep 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2016-6839 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2016-6839/ (Markdown: https://insights.sbomify.com/CVE-2016-6839/index.md)","id":"CVE-2016-6839","markdown":"https://insights.sbomify.com/CVE-2016-6839/index.md","name":"CVE-2016-6839","record":{"aliases":["GHSA-3q32-62v8-wp6j"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Huawei FusionAccess","requires_auth":"none","summary":"Remote attackers can inject HTTP headers and split responses in Huawei FusionAccess, potentially bypassing security controls.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fusionaccess","vendor":"huawei"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-113","name":"Improper Neutralization of CRLF Sequences in HTTP Headers"}],"description":"CRLF injection vulnerability in Huawei FusionAccess before V100R006C00 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via unspecified vectors.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Other in n/a","id":"CVE-2016-6839","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2016-6840"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2016-6838"},"products":["n/a"],"published":"2016-09-07","related":[{"cvss_score":7.8,"headline":"Missing authorization in FusionAccess","id":"CVE-2020-9090","kev_date_added":null,"published":"2020-10-12"},{"cvss_score":7.5,"headline":"Denial of service in FusionAccess V100R005C10,V100R005C20","id":"CVE-2015-7844","kev_date_added":null,"published":"2017-04-02"},{"cvss_score":6.5,"headline":"Denial of service in FusionAccess","id":"CVE-2020-1825","kev_date_added":null,"published":"2020-06-15"},{"cvss_score":6.5,"headline":"Other in FusionAccess FusionAccess V100R005C10, FusionAccess V100R005C20","id":"CVE-2016-8779","kev_date_added":null,"published":"2017-04-02"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote attackers can inject HTTP headers and split responses in Huawei FusionAccess, potentially bypassing security controls.","url":"https://insights.sbomify.com/CVE-2016-6839/"}