LiveActive security incident?Get immediate response
CVE Record

CVE-2020-4175: IBM Security Guardium Insights 2.0.1 could allow a remote attacker to obtain sensitive information, caused...

IBM Security Guardium Insights 2.0.1 could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict Transport Security. An attacker could exploit this vulnerability to obtain sensitive information using man in the middle techniques. IBM X-Force ID: 174684.

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

Security readout for executives and security teams

Plain-English summary

IBM Security Guardium Insights 2.0.1 did not properly enforce HTTP Strict Transport Security. That could let an attacker in a man-in-the-middle position capture sensitive information. The issue is medium severity, but important where Guardium traffic crosses untrusted or shared networks.

Executive priority

Treat as a targeted confidentiality risk, not an emergency mass-exploitation issue. Prioritize remediation for exposed or remotely administered Guardium Insights 2.0.1 systems because the product handles security and database monitoring information.

Technical view

CVE-2020-4175 affects IBM Security Guardium Insights 2.0.1. The weakness is improper HSTS enablement, allowing sensitive information disclosure through man-in-the-middle techniques. CVSS 3.0 is 5.9 with network attack vector, no privileges, no user interaction, high confidentiality impact, and high attack complexity.

Likely exposure

Exposure is limited to IBM Security Guardium Insights version 2.0.1. Risk is higher for internet-accessible deployments, remote administration paths, or environments where TLS-terminating proxies and network paths are not tightly controlled.

Exploitation context

The provided sources do not show active exploitation, and this CVE is not listed as KEV. Exploitation requires man-in-the-middle conditions, which aligns with the high attack complexity in the CVSS vector.

Researcher notes

Evidence is clear on affected product, version, root cause, and impact. The bundle does not include detailed fixed-version information or exploitation telemetry beyond KEV=false, so validation should stay focused on version presence, HSTS behavior, and IBM guidance.

Mitigation direction

  • Review IBM advisory guidance for Guardium Insights 2.0.1 remediation.
  • Upgrade or apply vendor-approved fixes where IBM provides them.
  • Verify HSTS is correctly enabled after remediation or configuration changes.
  • Restrict Guardium administrative access to trusted networks.
  • Review TLS proxy or load balancer settings for HSTS handling.

Validation and detection

  • Inventory Guardium Insights deployments and confirm whether version 2.0.1 is present.
  • Check authorized HTTPS endpoints for correct HSTS response behavior.
  • Confirm administrative access paths do not traverse untrusted networks.
  • Review reverse proxy and load balancer configurations affecting security headers.
  • Document remediation evidence for vulnerability management tracking.
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.

cve · low confidence lookup

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

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

Vulnerability scoring details

Base CVSS 3.0 score

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

Vector: CVSS:3.0/S:U/I:N/C:H/A:N/AV:N/PR:N/UI:N/AC:H/E:U/RC:C/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 Guardium Insights2.0.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.