dbcve.org
Security Access ManagerApplication · Ibm

CVE-2023-38371

HIGH · 7.5 CVSS v3.1 Published 2024-06-27
Fix available
A fix is available. Upgrade to after 10.0.7.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM Security Access Manager Docker 10.0.0.0 through 10.0.7.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 261198.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

IBM Security Access Manager Docker versions 10.0.0.0 through 10.0.7.1 implements weaker than expected cryptographic algorithms, which could allow a remote attacker to decrypt highly sensitive information by exploiting the weak encryption protecting that data.

MitigationUpgrade IBM Security Access Manager Docker to a version beyond 10.0.7.1 that implements stronger cryptographic algorithms, and re-encrypt any sensitive data that may have been protected by the weaker algorithms.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Security Access ManagerApplication
Affected:>= 10.0.0.0, <= 10.0.7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed IBM Security Access Manager Docker version
    Run 'docker ps' to find the container name or ID, then run 'docker exec <container> cat /opt/ibm/sam/version' or check the container image tag that was used to deploy it
    Affected if The version cannot be determined or is not documented
  2. Confirm the deployment is the Docker variant
    Verify the environment uses containerized IBM Security Access Manager by checking for Docker or OpenShift container manifests, Kubernetes deployment files, or running 'docker images' to confirm the ISAM Docker image is present
    Affected if The product is not the Docker container variant but a traditional installation (different CVE may apply)
  3. Compare the installed version against the affected range
    Check if the version number is 10.0.0.0, 10.0.1.0, 10.0.2.0, 10.0.3.0, 10.0.4.0, 10.0.5.0, 10.0.6.0, or 10.0.7.1, or any version between 10.0.0.0 and 10.0.7.1 inclusive
    Affected if The installed version falls within >= 10.0.0.0 and <= 10.0.7.1
  4. Inspect for sensitive data protected by weak encryption
    Review any encrypted configuration files, credential stores, or data vaults within the container that may contain highly sensitive information protected by the application's built-in encryption
    Affected if Sensitive data exists in encrypted storage within a vulnerable version

A defender is affected if they are running IBM Security Access Manager Docker version 10.0.0.0 through 10.0.7.1, inclusive, regardless of whether weak-encrypted sensitive data is confirmed to exist.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 10.0.7.1
Interim mitigation

Upgrade IBM Security Access Manager Docker to a version beyond 10.0.7.1 that implements stronger cryptographic algorithms, and re-encrypt any sensitive data that may have been protected by the weaker algorithms.

Recommended fix Moderate confidence

IBM Security Access Manager Docker version > 10.0.7.1 (consult IBM for specific fixed release)

  1. 1. Identify the current IBM Security Access Manager Docker version in use (e.g., docker images or container inspect)
  2. 2. Review IBM's official security bulletins for IBM Security Access Manager or IBM Security Verify Access for the fixed release
  3. 3. Plan upgrade considering your deployment architecture and dependencies
  4. 4. Backup all configuration data and certificates before upgrading
  5. 5. Pull the new fixed Docker image from IBM's entitled Docker registry
  6. 6. Update Docker deployment configuration to use the fixed version
  7. 7. Verify the container starts successfully and cryptographic configurations are updated
  8. 8. Test authentication and encryption functionality to confirm remediation
Caveat Review IBM migration guide for configuration changes between versions; test thoroughly in non-production first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Security Access Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-38371 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-38371 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data