CVE-2017-1395
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM Security Identity Governance and Intelligence Virtual Appliance 5.2 through 5.2.3.2 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: 127341.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIBM Security Identity Governance and Intelligence Virtual Appliance versions 5.2 through 5.2.3.2 fail to properly enable HTTP Strict Transport Security (HSTS). Without HSTS headers configured, browsers will accept both HTTP and HTTPS connections, allowing man-in-the-middle attackers to intercept sensitive information by downgrading connections to unencrypted HTTP or impersonating the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 5.2, <= 5.2.3.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm the installed IBM IGI versionRun the command to display the product version (typically 'product version' or similar command on the Virtual Appliance). Compare the output against the affected range: 5.2 through 5.2.3.2.Affected if The installed version falls within 5.2 to 5.2.3.2 inclusive.
-
Check for HSTS header in HTTP responseUse a tool like curl to request the application's login page or any HTTPS endpoint: 'curl -I https://<igi-host>/<app-path>'. Look for the 'Strict-Transport-Security' header in the response headers.Affected if The Strict-Transport-Security header is missing from HTTPS responses.
-
Inspect IBM HTTP Server configuration for HSTSLocate the IBM HTTP Server configuration file (typically httpd.conf or a included .conf file in the IHS config directory). Search for 'Header set Strict-Transport-Security' or 'HSTS' directives.Affected if No HSTS header directive is configured in the web server configuration.
-
Test HTTP to HTTPS redirect behaviorMake an HTTP request (not HTTPS) to the application: 'curl -I http://<igi-host>'. Observe whether the server automatically redirects to HTTPS or allows the unencrypted connection to proceed.Affected if The server accepts plain HTTP connections without forcing a redirect to HTTPS.
A user is affected if they are running IBM Security Identity Governance and Intelligence version 5.2 through 5.2.3.2 and the web server does not send Strict-Transport-Security headers, allowing unencrypted HTTP connections.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataEnable HSTS headers on the web server (typically IBM HTTP Server) to enforce HTTPS-only connections and protect against man-in-the-middle attacks.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1395 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-1395 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data