{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-35137 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-35137 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-35137 is a medium-severity vulnerability in IBM Security Verify Access Docker, published on 28 Jun 2024. 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-2024-35137 and fix it if it is affected.\n\nWhat it is: CVE-2024-35137 is a medium-severity vulnerability in IBM Security Verify Access Docker, published on 28 Jun 2024. 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-2024-35137 in the wild and no public exploit code.\n\nAffected product: IBM Security Verify Access Docker. 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-2024-35137/ (Markdown: https://insights.sbomify.com/CVE-2024-35137/index.md)","id":"CVE-2024-35137","markdown":"https://insights.sbomify.com/CVE-2024-35137/index.md","name":"CVE-2024-35137","record":{"aliases":["GHSA-jhrr-7ggp-3gv3"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IBM Security Access Manager","requires_auth":"none","summary":"A local user can access sensitive configuration data in IBM Security Access Manager Docker, potentially leading to privilege escalation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"security_access_manager","vendor":"ibm"}],"cvss":{"score":6.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-521","name":"Weak Password Requirements"},{"id":"CWE-258","name":"Empty Password in Configuration File"}],"description":"IBM Security Access Manager Docker 10.0.0.0 through 10.0.7.1 could allow a local user to possibly elevate their privileges due to sensitive configuration information being exposed.   IBM X-Force ID:  292413.","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":"IBM Security Access Manager Docker information disclosure","id":"CVE-2024-35137","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"IBM Security Verify Access cross-site request forgery","id":"CVE-2024-35138"},"packages":[],"prev":{"headline":"IBM Db2 denial of service","id":"CVE-2024-35136"},"products":["Security Verify Access Docker"],"published":"2024-06-28","related":[{"cvss_score":10,"headline":"Code injection in Security Access Manager Appliance","id":"CVE-2018-1722","kev_date_added":null,"published":"2018-08-24"},{"cvss_score":9.1,"headline":"Command injection in n/a","id":"CVE-2016-3028","kev_date_added":null,"published":"2016-11-25"},{"cvss_score":8.8,"headline":"Missing authorization in Security Access Manager Appliance","id":"CVE-2018-1850","kev_date_added":null,"published":"2018-10-22"},{"cvss_score":8.1,"headline":"Security feature bypass in n/a","id":"CVE-2016-3025","kev_date_added":null,"published":"2016-11-25"},{"cvss_score":7.8,"headline":"IBM Security Access Manager Docker privilege escalation","id":"CVE-2023-30997","kev_date_added":null,"published":"2024-06-27"},{"cvss_score":7.8,"headline":"IBM Security Access Manager Docker privilege escalation","id":"CVE-2023-30998","kev_date_added":null,"published":"2024-06-27"},{"cvss_score":7.7,"headline":"Information disclosure in Security Access Manager","id":"CVE-2019-4145","kev_date_added":null,"published":"2019-06-25"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-03","vendors":["IBM"]},"summary":"A local user can access sensitive configuration data in IBM Security Access Manager Docker, potentially leading to privilege escalation.","url":"https://insights.sbomify.com/CVE-2024-35137/"}