dbcve.org
Security Guardium Big Data IntelligenceApplication · Ibm

CVE-2018-1377

HIGH · 7.8 CVSS v3.0 Published 2018-02-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
IBM Security Guardium Big Data Intelligence (SonarG) 3.1 stores user credentials in plain in clear text which can be read by a local user. IBM X-Force ID: 137778.

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 confidence

IBM Security Guardium Big Data Intelligence (SonarG) version 3.1 stores user credentials in plaintext rather than using proper cryptographic hashing or encryption. A local user with filesystem access can read these unencrypted credentials, potentially gaining unauthorized access to other user accounts or administrative functions.

MitigationUpgrade to a patched version of IBM Security Guardium Big Data Intelligence that implements proper credential hashing or encryption at rest. If no patch is available, implement compensating controls such as restricting filesystem access and monitoring for unauthorized access attempts.

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
Security Guardium Big Data IntelligenceApplication
Affected:= 3.1

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed product version
    Locate and inspect the IBM Security Guardium Big Data Intelligence installation directory, then run 'version' command or check version file to confirm the installed version number
    Affected if Installed version is exactly 3.1 (no patches applied)
  2. Locate credential storage location
    Find directories or configuration files where user credentials are stored within the SonarG application data, typically in config or data subdirectories under the installation root
    Affected if Credential storage directories exist on the filesystem and are accessible to local users
  3. Inspect credential files for plaintext storage
    Open and read credential-related files using a text editor or file inspection command - examine whether password values appear as readable text rather than hashed or encrypted strings
    Affected if Password values in credential files are readable plaintext strings (not base64, not salted hashes, not encrypted)
  4. Verify filesystem permissions on credential files
    Use 'ls -la' or equivalent command to list file permissions on credential storage files and confirm whether read access is granted to non-privileged users
    Affected if Credential files are readable by users other than the application owner (world-readable or group-readable)
  5. Compare against expected cryptographic format
    Examine credential storage format - properly implemented credentials should use salted bcrypt, PBKDF2, or similar cryptographic hashing, not raw plaintext or simple encoding
    Affected if Credentials are stored without cryptographic transformation (raw plaintext, simple base64, or reversible encoding only)

Your environment is affected if IBM Security Guardium Big Data Intelligence version 3.1 is installed and credential files contain readable plaintext passwords accessible to local filesystem users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of IBM Security Guardium Big Data Intelligence that implements proper credential hashing or encryption at rest. If no patch is available, implement compensating controls such as restricting filesystem access and monitoring for unauthorized access attempts.

Fix this in Security Guardium Big Data Intelligence Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1377 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1377 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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