dbcve.org
HTTP ServerWeb server / proxy · Ibm

CVE-2015-4947

HIGH · 9.0 CVSS v2.0 Published 2015-09-15
Fix available
A fix is available. Upgrade to 7.0.0.39 / 8.0.0.12 or later.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable 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
Stack-based buffer overflow in the Administration Server in IBM HTTP Server 6.1.0.x through 6.1.0.47, 7.0.0.x before 7.0.0.39, 8.0.0.x before 8.0.0.12, and 8.5.x before 8.5.5.7, as used in WebSphere Application Server and other products, allows remote authenticated users to execute arbitrary code via unspecified vectors.

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

Stack-based buffer overflow in the Administration Server component of IBM HTTP Server allows remote authenticated users to execute arbitrary code. The vulnerability affects versions 6.1.0.x through 6.1.0.47, 7.0.0.x before 7.0.0.39, 8.0.0.x before 8.0.0.12, and 8.5.x before 8.5.5.7.

MitigationUpgrade IBM HTTP Server to version 6.1.0.48 or later, 7.0.0.39 or later, 8.0.0.12 or later, or 8.5.5.7 or later. If immediate patching is not possible, restrict Administration Server access to trusted networks or disable remote administration until the upgrade can be applied.

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
HTTP ServerWeb server / proxy
Affected:>= 6.1.0.0, <= 6.1.0.47>= 7.0.0.0, < 7.0.0.39>= 8.0.0.0, < 8.0.0.12>= 8.5.0.0, < 8.5.5.7

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
Network
Complexity
Low
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/C:C/I:C/A:C

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 IBM HTTP Server installation and version
    Run the command 'httpd -v' (or 'apachectl -v') from the IBM HTTP Server bin directory, or check the version file in the installation directory. On Windows, check the version via the IBM HTTP Server program properties.
    Affected if The version falls within 6.1.0.0-6.1.0.47, 7.0.0.0-7.0.0.38, 8.0.0.0-8.0.0.11, or 8.5.0.0-8.5.5.6.
  2. Confirm version is affected by CVE-2015-4947
    Compare your installed IBM HTTP Server version number against the affected ranges: 6.1.0.x through 6.1.0.47, 7.0.0.x before 7.0.0.39, 8.0.0.x before 8.0.0.12, or 8.5.x before 8.5.5.7.
    Affected if The installed version matches any of these affected ranges.
  3. Verify Administration Server component is configured
    Check if the IBM Administration Server (admin.conf or similar configuration) is enabled. Look for Administration Server configuration files in the IHS conf directory and verify the admin server process is configured to run.
    Affected if The Administration Server component is enabled or configured to run, even if not exposed externally.
  4. Check Administration Server network exposure
    Review the Administration Server configuration for listening interfaces (for example, examine Listen directives and admin.conf BindAddress settings). Determine if the admin port is accessible from untrusted networks.
    Affected if The Administration Server is reachable from non-trusted network segments or the internet.

You are affected if IBM HTTP Server version falls within the vulnerable ranges AND the Administration Server component is enabled and accessible.

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.

dbcve · scoped
Upgrade available Upgrade to 7.0.0.39 / 8.0.0.12 / 8.5.5.7 or later
Fixed in 7.0.0.398.0.0.128.5.5.7
Interim mitigation

Upgrade IBM HTTP Server to version 6.1.0.48 or later, 7.0.0.39 or later, 8.0.0.12 or later, or 8.5.5.7 or later. If immediate patching is not possible, restrict Administration Server access to trusted networks or disable remote administration until the upgrade can be applied.

Recommended fix High confidence

IBM HTTP Server 7.0.0.39+ / 8.0.0.12+ / 8.5.5.7+ (6.1.x line has no fix; migrate to supported version)

  1. 1. Identify the currently installed IBM HTTP Server version and edition
  2. 2. For HTTP Server 6.1.x: IBM HTTP Server 6.1 reached end of support; migrate to a supported version (7.0.0.39+, 8.0.0.12+, or 8.5.5.7+)
  3. 3. For HTTP Server 7.0.0.x: Upgrade to version 7.0.0.39 or later
  4. 4. For HTTP Server 8.0.0.x: Upgrade to version 8.0.0.12 or later
  5. 5. For HTTP Server 8.5.x: Upgrade to version 8.5.5.7 or later
  6. 6. Download the appropriate fix pack from IBM Fix Central (www-01.ibm.com)
  7. 7. Review IBM migration guides for configuration changes between major versions
  8. 8. Test the upgrade in a non-production environment before deploying
Caveat Upgrading major versions (especially 6.1 to 7.0/8.x) may require configuration file updates and compatibility testing; IBM HTTP Server 6.1.x is end-of-life with no patch available

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in HTTP Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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