LiveActive security incident?Get immediate response
CVE Record

CVE-2021-29699: IBM Security Verify Access Docker 10.0.0 could allow a remote priviled user to upload arbitrary files with...

IBM Security Verify Access Docker 10.0.0 could allow a remote priviled user to upload arbitrary files with a dangerous file type that could be excuted by an user. IBM X-Force ID: 200600.

MediumCVSS 6.6Not 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 has a file upload weakness. A remote privileged user could upload a dangerous file type that may later be executed by a user. This is not a broad unauthenticated internet issue in the provided evidence, but it can still create serious business risk where privileged access is mishandled.

Executive priority

Prioritize remediation during the next security maintenance window if version 10.0.0 is present. Escalate sooner if privileged access is broadly shared, externally reachable, or poorly monitored.

Technical view

The issue is an arbitrary dangerous file-type upload flaw in IBM Security Verify Access Docker 10.0.0. The provided CVSS 3.0 score is 6.6. The vector indicates high privileges and user interaction are required, with high confidentiality and integrity impact if successful. IBM X-Force tracks it as ID 200600.

Likely exposure

Exposure is limited by the provided sources to IBM Security Verify Access Docker version 10.0.0. Organizations should confirm whether this exact container version exists in production, staging, or retained deployment artifacts.

Exploitation context

The source bundle does not cite active exploitation, and the CVE is not marked as CISA KEV. IBM’s provided vector lists exploit maturity as unproven. Treat this as a remediation and access-control priority, not confirmed emergency exploitation.

Researcher notes

Evidence is narrow: affected product and version, CVSS, and IBM X-Force ID are provided. No CWE, proof-of-concept status, exploit details, or concrete patch version are included in the bundle. Avoid assuming broader IBM Security Verify Access versions are affected.

Mitigation direction

  • Review IBM advisory node 6471895 for official remediation guidance.
  • Apply IBM-provided fixes or upgrade guidance for affected 10.0.0 deployments.
  • Restrict privileged access to Security Verify Access Docker administration paths.
  • Review upload controls for dangerous file types in affected deployments.
  • Monitor vendor guidance for any updated fixes or indicators.

Validation and detection

  • Inventory IBM Security Verify Access Docker versions across all environments.
  • Confirm whether version 10.0.0 is deployed or retained in images.
  • Check privileged account access paths to affected systems.
  • Review logs for suspicious file upload activity by privileged users.
  • Verify remediation against IBM’s advisory after applying vendor guidance.
Prepared
Confidence
medium
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

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-29699 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.6 (3.0)
Known Exploited
No
Published

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

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.6CVSS 3.0MediumCVSS:3.0/AV:A/A:H/AC:L/S:U/I:H/C:H/UI:R/PR:H/RC:C/E:U/RL:O0.75.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

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

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

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.