dbcve.org
Security AppscanApplication · Ibm

CVE-2014-4806

MEDIUM · 5.5 CVSS v3.1 Published 2014-08-29
Fix available
A fix is available. Upgrade to 8.6.0.2 / 8.7.0.1 or later.
See remediation →
57/100
Remediation priority · Elevated
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
The installation process in IBM Security AppScan Enterprise 8.x before 8.6.0.2 iFix 003, 8.7.x before 8.7.0.1 iFix 003, 8.8.x before 8.8.0.1 iFix 002, and 9.0.x before 9.0.0.1 iFix 001 on Linux places a cleartext password in a temporary file, which allows local users to obtain sensitive information by reading this file.

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

During the installation process of IBM Security AppScan Enterprise on Linux, the installer creates a temporary file that contains a cleartext password. Any local user with access to the system can read this file to obtain the sensitive password information.

MitigationApply the relevant iFix patches (8.6.0.2 iFix 003, 8.7.0.1 iFix 003, 8.8.0.1 iFix 002, or 9.0.0.1 iFix 001) to the affected versions. Additionally, identify and remove any residual temporary installation files and rotate any passwords that may have been exposed.

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 AppscanApplication
Affected:>= 8.0.0.0, < 8.6.0.2>= 8.7.0.0, < 8.7.0.1>= 8.8.0.0, < 8.8.0.1>= 9.0.0.0, < 9.0.0.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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

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

  1. Check if IBM Security AppScan Enterprise is installed
    Look for AppScan Enterprise installation directories on Linux, such as in /opt/IBM or /usr/local, or search for the product using package management tools if installed via system packages.
    Affected if The product is present on the system and was installed on Linux.
  2. Locate temporary installation files containing passwords
    Search the filesystem for temporary or log files created during installation that may contain cleartext passwords. Check common temporary directories such as /tmp, the installation working directory, and any installation logs. Look for files with patterns indicating they are temporary or related to the installation process.
    Affected if A temporary file from installation exists and contains readable password data.
  3. Identify the installed AppScan Enterprise version
    Locate the version information for the installation, typically found in version files, About dialogs, or product-specific configuration files within the AppScan installation directory.
    Affected if The installed version falls within any of the affected ranges: 8.0.0.0 through 8.6.0.1, 8.7.0.0, 8.7.0.1 through 8.7.0.0 (note: 8.7.0.1 is fixed), 8.8.0.0 through 8.8.0.0 (note: 8.8.0.1 is fixed), or 9.0.0.0.
  4. Examine file permissions on installation artifacts
    Review file permissions on installation directories, temporary files, and logs to determine if non-privileged local users have read access to sensitive installation files.
    Affected if Files containing password information are readable by users other than the installer or administrator.

A system is affected if IBM Security AppScan Enterprise is installed on Linux, a temporary file from installation with cleartext passwords exists and is readable, and the installed version falls within the affected version ranges.

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
Upgrade available Upgrade to 8.6.0.2 / 8.7.0.1 / 8.8.0.1 or later
Fixed in 8.6.0.28.7.0.18.8.0.1
Interim mitigation

Apply the relevant iFix patches (8.6.0.2 iFix 003, 8.7.0.1 iFix 003, 8.8.0.1 iFix 002, or 9.0.0.1 iFix 001) to the affected versions. Additionally, identify and remove any residual temporary installation files and rotate any passwords that may have been exposed.

Fix this in Security Appscan Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-4806 — 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-2014-4806 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