{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-6102 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-6102 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-6102 is a low-severity vulnerability in Ibm Security Key Lifecycle Manager, published on 27 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-6102 and fix it if it is affected.\n\nWhat it is: CVE-2016-6102 is a low-severity vulnerability in Ibm Security Key Lifecycle Manager, published on 27 Mar 2017. 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-2016-6102 in the wild and no public exploit code.\n\nAffected product: Ibm Security Key Lifecycle Manager. 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-6102/ (Markdown: https://insights.sbomify.com/CVE-2016-6102/index.md)","id":"CVE-2016-6102","markdown":"https://insights.sbomify.com/CVE-2016-6102/index.md","name":"CVE-2016-6102","record":{"aliases":["GHSA-43xh-2p22-hgf8"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Key Lifecycle Manager","requires_auth":"none","summary":"Attackers can access sensitive information stored in URL parameters via logs or history, requiring IBM to patch the Key Lifecycle Manager.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"security_key_lifecycle_manager","vendor":"ibm"}],"cvss":{"score":3.7,"severity":"low","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"IBM Tivoli Key Lifecycle Manager 2.5 and 2.6 stores sensitive information in URL parameters. This may lead to information disclosure if unauthorized parties have access to the URLs via server logs, referrer header or browser history. IBM Reference #: 2000359.","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":"Information disclosure in Key Lifecycle Manager","id":"CVE-2016-6102","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:security_key_lifecycle_manager","products":["ibm:security_key_lifecycle_manager"],"type":"information_disclosure","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site request forgery in Key Lifecycle Manager","id":"CVE-2016-6103"},"packages":[],"prev":{"headline":"Cross-site request forgery in Atlas Policy Suite","id":"CVE-2016-6100"},"products":["Key Lifecycle Manager"],"published":"2017-03-27","related":[{"cvss_score":9.8,"headline":"SQL injection in Security Key Lifecycle Manager","id":"CVE-2017-1670","kev_date_added":null,"published":"2018-01-09"},{"cvss_score":9.8,"headline":"Weak cryptography in Security Key Lifecycle Manager","id":"CVE-2016-6093","kev_date_added":null,"published":"2017-06-08"},{"cvss_score":9.8,"headline":"Security feature bypass in Key Lifecycle Manager","id":"CVE-2016-6095","kev_date_added":null,"published":"2017-02-02"},{"cvss_score":8.8,"headline":"Cross-site request forgery in Security Key Lifecycle Manager","id":"CVE-2017-1672","kev_date_added":null,"published":"2018-01-04"},{"cvss_score":8.8,"headline":"Cross-site request forgery in Key Lifecycle Manager","id":"CVE-2016-6103","kev_date_added":null,"published":"2017-02-02"},{"cvss_score":8.6,"headline":"Security feature bypass in Security Key Lifecycle Manager","id":"CVE-2020-4567","kev_date_added":null,"published":"2020-07-29"},{"cvss_score":8.2,"headline":"Missing authorization in Key Lifecycle Manager","id":"CVE-2016-6105","kev_date_added":null,"published":"2017-02-01"}],"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":["IBM Corporation"]},"summary":"Attackers can access sensitive information stored in URL parameters via logs or history, requiring IBM to patch the Key Lifecycle Manager.","url":"https://insights.sbomify.com/CVE-2016-6102/"}