LiveActive security incident?Get immediate response
CVE Record

CVE-2020-4190: IBM Security Guardium 10.6, 11.0, and 11.1 contains hard-coded credentials, such as a password or cryptogra...

IBM Security Guardium 10.6, 11.0, and 11.1 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: 174851.

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

Security readout for executives and security teams

Plain-English summary

IBM Security Guardium 10.6, 11.0, and 11.1 used hard-coded credentials or keys. An attacker would need local access, high privileges, and difficult conditions, but successful abuse could expose confidential information. The sources do not show active exploitation.

Executive priority

Treat as a moderate-priority remediation item. It affects a security monitoring product and could expose confidential data, but available evidence shows demanding exploitation conditions and no confirmed active exploitation.

Technical view

CVE-2020-4190 is a hard-coded credential issue in IBM Security Guardium. The CVSS v3.0 vector is AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N, indicating local, high-complexity exploitation requiring high privileges, with confidentiality impact only. IBM X-Force tracks it as ID 174851.

Likely exposure

Exposure is limited to organizations running IBM Security Guardium versions 10.6, 11.0, or 11.1. Risk is most relevant where privileged local users, administrators, or compromised management access can reach Guardium systems.

Exploitation context

The CVE is not listed as CISA KEV in the provided bundle, and the CVSS temporal metric marks exploitability as unproven. No cited source in the bundle reports active exploitation.

Researcher notes

Evidence is limited to CVE, IBM advisory, and IBM X-Force metadata. The bundle does not provide detailed vulnerable component paths, proof-of-concept status, or named fixed versions, so validation should stay version- and vendor-guidance based.

Mitigation direction

  • Check IBM advisory for the vendor-approved remediation path.
  • Apply IBM-provided fixes or upgrade guidance for affected Guardium versions.
  • Restrict privileged local access to Guardium systems.
  • Review administrative access controls and credential handling.
  • Rotate relevant credentials or keys if IBM guidance recommends it.

Validation and detection

  • Inventory Guardium deployments and confirm exact versions.
  • Flag Guardium 10.6, 11.0, and 11.1 as affected.
  • Verify remediation status against IBM support guidance.
  • Review privileged local access to Guardium hosts.
  • Check security monitoring for unusual administrative access.
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
cve · low confidence lookup

CVE-2020-4190 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
4.1 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/UI:N/C:H/PR:H/AC:H/I:N/AV:L/A:N/S:U/RL:O/E:U/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
4.1CVSS 3.0MediumCVSS:3.0/UI:N/C:H/PR:H/AC:H/I:N/AV:L/A:N/S:U/RL:O/E:U/RC:C0.53.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

4.1Medium
CVSS 3.0 vector shape for CVE-2020-4190Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/UI:N/C:H/PR:H/AC:H/I:N/AV:L/A:N/S:U/RL:O/E:U/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 Guardium10.6, 11.0, 11.1Listed
Weakness

CWE details

No CWE listed

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