{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2023-32327 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-32327 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-32327 is a high-severity vulnerability in Ibm Security Verify Access, published on 3 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-32327 and fix it if it is affected.\n\nWhat it is: CVE-2023-32327 is a high-severity vulnerability in Ibm Security Verify Access, published on 3 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-32327 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-32327/ (Markdown: https://insights.sbomify.com/CVE-2023-32327/index.md)","id":"CVE-2023-32327","markdown":"https://insights.sbomify.com/CVE-2023-32327/index.md","name":"CVE-2023-32327","record":{"aliases":["GHSA-gg63-hgm5-v538"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Security Access Manager","requires_auth":"low_privilege","summary":"Remote attackers can exploit XML External Entity injection in IBM Security Access Manager to expose sensitive information or cause denial of service.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"security_verify_access","vendor":"ibm"},{"product":"security_verify_access_docker","vendor":"ibm"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"}],"description":"IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.0.0 through 10.0.6.1) is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources.  IBM X-Force ID:  254783.","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 Container XML external entity injection","id":"CVE-2023-32327","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:security_verify_access","products":["ibm:security_verify_access"],"type":"xxe","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"IBM Security Verify Access information disclosure","id":"CVE-2023-32328"},"packages":[],"prev":{"headline":"Cross-site scripting in PostHog-js","id":"CVE-2023-32325"},"products":["Security Verify Access Appliance","Security Verify Access Docker"],"published":"2024-02-03","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":"2025-11-03","vendors":["IBM"]},"summary":"Remote attackers can exploit XML External Entity injection in IBM Security Access Manager to expose sensitive information or cause denial of service.","url":"https://insights.sbomify.com/CVE-2023-32327/"}