{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-3039 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-3039 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-3039 is a high-severity vulnerability in n/a, published on 17 Jul 2016. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-3039 and fix it if it is affected.\n\nWhat it is: CVE-2016-3039 is a high-severity vulnerability in n/a, published on 17 Jul 2016. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-3039 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-3039/ (Markdown: https://insights.sbomify.com/CVE-2016-3039/index.md)","id":"CVE-2016-3039","markdown":"https://insights.sbomify.com/CVE-2016-3039/index.md","name":"CVE-2016-3039","record":{"aliases":["GHSA-xpx7-5x44-3fqq"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Traveler","requires_auth":"low_privilege","summary":"Authenticated attackers can read arbitrary files or cause denial of service via XML External Entity attacks in IBM Traveler.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"traveler","vendor":"ibm"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","version":"3.0"},"cwes":[],"description":"IBM Traveler 8.x and 9.x before 9.0.1.12 allows remote authenticated users to read arbitrary files or cause a denial of service (memory consumption) via XML data containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) 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":null,"headline":"XML external entity in n/a","id":"CVE-2016-3039","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xxe","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"Open redirect in n/a","id":"CVE-2016-3040"},"packages":[],"prev":{"headline":"Cross-site scripting in Cognos TM1","id":"CVE-2016-3038"},"products":["n/a"],"published":"2016-07-17","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Authenticated attackers can read arbitrary files or cause denial of service via XML External Entity attacks in IBM Traveler.","url":"https://insights.sbomify.com/CVE-2016-3039/"}