{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2016-0252 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-0252 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-0252 is a medium-severity vulnerability in n/a, published on 8 Jul 2016. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-0252 and fix it if it is affected.\n\nWhat it is: CVE-2016-0252 is a medium-severity vulnerability in n/a, published on 8 Jul 2016. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-0252 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-0252/ (Markdown: https://insights.sbomify.com/CVE-2016-0252/index.md)","id":"CVE-2016-0252","markdown":"https://insights.sbomify.com/CVE-2016-0252/index.md","name":"CVE-2016-0252","record":{"aliases":["GHSA-3cmp-c3h3-9xgc"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IBM Control Center","requires_auth":"none","summary":"Local users can decrypt the master key in IBM Control Center, exposing sensitive cryptographic material.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"control_center","vendor":"ibm"},{"product":"sterling_control_center","vendor":"ibm"}],"cvss":{"score":5.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"IBM Control Center 6.x before 6.0.0.1 iFix06 and Sterling Control Center 5.4.x before 5.4.2.1 iFix09 allow local users to decrypt the master key 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":"Information disclosure in n/a","id":"CVE-2016-0252","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2016"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2016-0253"},"packages":[],"prev":{"headline":"XML external entity in n/a","id":"CVE-2016-0250"},"products":["n/a"],"published":"2016-07-08","related":[{"cvss_score":7.1,"headline":"XML external entity in Control Center","id":"CVE-2017-1758","kev_date_added":null,"published":"2018-02-21"},{"cvss_score":5.4,"headline":"IBM Control Center cross-site scripting","id":"CVE-2024-35112","kev_date_added":null,"published":"2025-01-25"},{"cvss_score":5.4,"headline":"Cross-site scripting in Control Center","id":"CVE-2021-20528","kev_date_added":null,"published":"2021-05-19"},{"cvss_score":5.3,"headline":"IBM Control Center external service interaction","id":"CVE-2023-43052","kev_date_added":null,"published":"2025-03-07"},{"cvss_score":5.3,"headline":"IBM Control Center information disclosure","id":"CVE-2024-35114","kev_date_added":null,"published":"2025-01-25"},{"cvss_score":5.3,"headline":"Information disclosure in Control Center","id":"CVE-2021-20529","kev_date_added":null,"published":"2021-05-19"}],"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-05","vendors":["n/a"]},"summary":"Local users can decrypt the master key in IBM Control Center, exposing sensitive cryptographic material.","url":"https://insights.sbomify.com/CVE-2016-0252/"}