LiveActive security incident?Get immediate response
CVE Record

CVE-2017-1271: IBM Security Guardium 9.0, 9.1, and 9.5 supports interaction between multiple actors and allows those actor...

IBM Security Guardium 9.0, 9.1, and 9.5 supports interaction between multiple actors and allows those actors to negotiate which algorithm should be used as a protection mechanism such as encryption or authentication, but it does not select the strongest algorithm that is available to both parties. IBM X-Force ID: 124746.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

IBM Security Guardium 9.0, 9.1, and 9.5 may choose a weaker shared protection algorithm during encryption or authentication negotiation instead of the strongest mutually available option. That can reduce the strength of security controls protecting Guardium communications or authentication flows, but the provided sources do not include severity, CVSS, exploit evidence, or a named fix. Exposure is limited to environments running IBM Security Guardium 9.0, 9.1, or 9.5. Risk depends on where affected negotiation occurs, which algorithms are enabled, and whether relevant interfaces are reachable by untrusted or lower-trust actors. The supplied evidence does not identify affected deployment modes or network prerequisites. Handle as a targeted vendor follow-up, not an emergency based on current evidence. Prioritize quickly if affected Guardium systems protect sensitive or regulated data, are exposed beyond tightly controlled networks, or cannot be aligned with vendor-supported cryptographic settings. Mitigation focus: Inventory IBM Security Guardium deployments and identify versions 9.0, 9.1, and 9.5.; Review IBM advisory swg22010435 and X-Force ID 124746 for vendor-approved remediation.; If guidance is unavailable, open an IBM support case before changing production cryptographic settings..

Prepared

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-2017-1271 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IBMSecurity Guardium9.0, 9.1, 9.5Listed
Weakness

CWE details

No CWE listed

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