{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-38341 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-38341 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-38341 is a medium-severity vulnerability in IBM Sterling Secure Proxy, published on 28 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-38341 and fix it if it is affected.\n\nWhat it is: CVE-2024-38341 is a medium-severity vulnerability in IBM Sterling Secure Proxy, published on 28 May 2025. 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-2024-38341 in the wild and no public exploit code.\n\nAffected product: IBM Sterling Secure Proxy. 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-38341/ (Markdown: https://insights.sbomify.com/CVE-2024-38341/index.md)","id":"CVE-2024-38341","markdown":"https://insights.sbomify.com/CVE-2024-38341/index.md","name":"CVE-2024-38341","record":{"aliases":["GHSA-7xpv-834v-x9rj"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Secure Proxy","requires_auth":"none","summary":"Attackers can decrypt highly sensitive information due to weak cryptographic algorithms in IBM Sterling Secure Proxy.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"sterling_secure_proxy","vendor":"ibm"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-326","name":"Inadequate Encryption Strength"},{"id":"CWE-328","name":"Use of Weak Hash"}],"description":"IBM Sterling Secure Proxy 6.0.0.0 through 6.0.3.1, 6.1.0.0 through 6.1.0.0, and 6.2.0.0 through 6.2.0.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.","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 Sterling Secure Proxy information disclosure","id":"CVE-2024-38341","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site request forgery in WP Tweet Walls","id":"CVE-2024-38344"},"packages":[],"prev":{"headline":"IBM Sterling Secure Proxy improper input validation","id":"CVE-2024-38337"},"products":["Sterling Secure Proxy"],"published":"2025-05-28","related":[{"cvss_score":9.1,"headline":"IBM Sterling Secure Proxy improper input validation","id":"CVE-2024-38337","kev_date_added":null,"published":"2025-01-19"},{"cvss_score":9.1,"headline":"IBM Sterling Secure Proxy improper input validation","id":"CVE-2024-41783","kev_date_added":null,"published":"2025-01-19"},{"cvss_score":7.5,"headline":"IBM Sterling Secure Proxy directory traversal","id":"CVE-2024-41784","kev_date_added":null,"published":"2024-11-15"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2016-6023","kev_date_added":null,"published":"2016-10-06"},{"cvss_score":6.1,"headline":"IBM Secure Proxy cross-site scripting","id":"CVE-2023-47162","kev_date_added":null,"published":"2024-03-15"},{"cvss_score":6.1,"headline":"IBM Secure Proxy cross-site scripting","id":"CVE-2023-47699","kev_date_added":null,"published":"2024-03-15"},{"cvss_score":6.1,"headline":"Security feature bypass in n/a","id":"CVE-2016-6027","kev_date_added":null,"published":"2016-10-06"}],"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-08-16","vendors":["IBM"]},"summary":"Attackers can decrypt highly sensitive information due to weak cryptographic algorithms in IBM Sterling Secure Proxy.","url":"https://insights.sbomify.com/CVE-2024-38341/"}