LiveActive security incident?Get immediate response
CVE Record

CVE-2021-20537: IBM Security Verify Access Docker 10.0.0 contains hard-coded credentials, such as a password or cryptograph...

IBM Security Verify Access Docker 10.0.0 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. IBM X-Force ID:198918

MediumCVSS 6.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

IBM Security Verify Access Docker 10.0.0 includes hard-coded credentials used for authentication, external communication, or internal encryption. This can expose sensitive data if an attacker already has low-privileged access. The issue is medium severity, but confidentiality impact is high.

Executive priority

Prioritize remediation for any internet-reachable or sensitive Identity and Access Management deployment. Treat this as a confidentiality risk, not a broad system takeover signal, based on the available sources.

Technical view

CVE-2021-20537 is a hard-coded credential weakness in IBM Security Verify Access Docker 10.0.0. The CVSS 3.0 vector is 6.5: network attack vector, low complexity, low privileges required, no user interaction, unchanged scope, high confidentiality impact, and no integrity or availability impact stated.

Likely exposure

Exposure appears limited to environments running IBM Security Verify Access Docker version 10.0.0. The source bundle does not identify other versions, products, CPEs, deployment modes, or cloud services as affected.

Exploitation context

The CVSS vector indicates exploitation is network-accessible but requires low privileges. The source bundle does not state public exploit availability or active exploitation, and KEV status is false.

Researcher notes

Evidence is limited to the CVE description, CVSS vector, IBM advisory reference, and X-Force entry. The bundle does not include specific credential details, affected build hashes, exploit procedures, or exact fixed version information.

Mitigation direction

  • Identify IBM Security Verify Access Docker 10.0.0 deployments in registries and runtime environments.
  • Follow IBM support guidance for the official remediation or fixed image.
  • Restrict network access to affected containers until remediation is complete.
  • Review related secrets and credentials for potential exposure.
  • Track IBM X-Force ID 198918 for vendor-specific details.

Validation and detection

  • Confirm whether any deployed image is IBM Security Verify Access Docker 10.0.0.
  • Compare deployed versions against IBM advisory guidance for CVE-2021-20537.
  • Verify affected containers are not broadly network-accessible.
  • Confirm remediation by checking the running image version after update.
  • Document residual exposure where upgrade timing is constrained.
Prepared
Confidence
high
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-20537 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AC:L/AV:N/A:N/C:H/UI:N/PR:L/I:N/S:U/E:U/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.0MediumCVSS:3.0/AC:L/AV:N/A:N/C:H/UI:N/PR:L/I:N/S:U/E:U/RL:O/RC:C2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

6.5Medium
CVSS 3.0 vector shape for CVE-2021-20537Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AC:L/AV:N/A:N/C:H/UI:N/PR:L/I:N/S:U/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IBMSecurity Verify Access Docker10.0.0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.