{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-30430 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-30430 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-30430 is a medium-severity vulnerability in Ibm Security Verify Access, published on 27 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-2023-30430 and fix it if it is affected.\n\nWhat it is: CVE-2023-30430 is a medium-severity vulnerability in Ibm Security Verify Access, published on 27 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-2023-30430 in the wild and no public exploit code.\n\nAffected product: Ibm Security Verify Access. 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-2023-30430/ (Markdown: https://insights.sbomify.com/CVE-2023-30430/index.md)","id":"CVE-2023-30430","markdown":"https://insights.sbomify.com/CVE-2023-30430/index.md","name":"CVE-2023-30430","record":{"aliases":["GHSA-6w48-6mx5-8f6c"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IBM Security Verify Access","requires_auth":"low_privilege","summary":"A local user can obtain sensitive information from trace logs in IBM Security Verify Access, requiring a patch to mitigate.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"security_verify_access","vendor":"ibm"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"IBM Security Verify Access 10.0.0 through 10.0.7.1 could allow a local user to obtain sensitive information from trace logs.  IBM X-Force ID:  252183.","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 Verify Access information disclosure","id":"CVE-2023-30430","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:security_verify_access","products":["ibm:security_verify_access"],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"IBM Db2 buffer overflow","id":"CVE-2023-30431"},"packages":[],"prev":{"headline":"Apache Pulsar: Incorrect Authorization for Function Worker when using mTLS Authentication through Pulsar Proxy","id":"CVE-2023-30429"},"products":["Security Verify Access"],"published":"2024-06-27","related":[{"cvss_score":9.8,"headline":"Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access","id":"CVE-2026-78401","kev_date_added":null,"published":"2026-10-08"},{"cvss_score":9.8,"headline":"Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access","id":"CVE-2026-78406","kev_date_added":null,"published":"2026-10-08"},{"cvss_score":9.8,"headline":"IBM Security Verify Access Appliance command execution","id":"CVE-2024-49803","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2021-39070","kev_date_added":null,"published":"2022-02-02"},{"cvss_score":9.4,"headline":"IBM Security Verify Access Appliance hard coded credentials","id":"CVE-2024-49805","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":9.4,"headline":"IBM Security Verify Access Appliance hard coded credentials","id":"CVE-2024-49806","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":9.3,"headline":"Security Vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access","id":"CVE-2026-1346","kev_date_added":null,"published":"2026-04-08"}],"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":"2024-08-24","vendors":["IBM"]},"summary":"A local user can obtain sensitive information from trace logs in IBM Security Verify Access, requiring a patch to mitigate.","url":"https://insights.sbomify.com/CVE-2023-30430/"}