dbcve.org
Websphere PortalApplication · Ibm

CVE-2015-7472

HIGH · 7.2 CVSS v3.0 Published 2016-02-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges 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 WebSphere Portal 6.1.0 through 6.1.0.6 CF27, 6.1.5 through 6.1.5.3 CF27, 7.0.0 through 7.0.0.2 CF29, 8.0.0 before 8.0.0.1 CF20, and 8.5.0 before CF10 allows remote attackers to conduct LDAP injection attacks, and consequently read or write to repository data, 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

IBM WebSphere Portal versions 6.1.0 through 8.5.0 contain an LDAP injection vulnerability allowing remote attackers to manipulate LDAP queries via unspecified vectors. This enables unauthorized read/write access to directory repository data by injecting special characters into LDAP statements.

MitigationApply the appropriate IBM WebSphere Portal Cumulative Fix (CF20 for 8.0.0.x, CF10 for 8.5.0, or later compatible CFs for earlier versions) to patch the LDAP injection vulnerability. Additionally, implement input validation on all user-supplied data that interfaces with LDAP directory queries.

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
Websphere PortalApplication
Affected:= 6.1.0.0= 6.1.0.1= 6.1.0.2= 6.1.0.3= 6.1.0.4= 6.1.0.5= 6.1.0.6= 6.1.5.0= 6.1.5.1= 6.1.5.2= 6.1.5.3= 7.0.0.0

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
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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. Identify the installed WebSphere Portal version
    Access the WebSphere Portal About page in the admin console (typically at /portal/html/about) or check the version file in the installation directory (Version.txt or about.xml in the PortalServer root). Compare the version number to the affected range: 6.1.0.0 through 6.1.5.3, 7.0.0.0, 8.0.0.x, and 8.5.0.
    Affected if The installed version falls within 6.1.0.0 through 8.5.0 (inclusive)
  2. Confirm LDAP repository is configured
    Log in to the WebSphere Application Server admin console and navigate to Security > Global Security > User account repository. Verify if LDAP is selected as the repository type, or check the wkplc.properties and wkplcldap.properties configuration files for LDAP repository settings.
    Affected if LDAP is configured as the user account repository or directory backend
  3. Verify LDAP query handling is in use
    Check if WebSphere Portal is using LDAP for user authentication, group membership, or directory lookup by examining the security configuration or running the Portal XML configuration interface to dump the security settings.
    Affected if Portal is actively querying the LDAP directory for user authentication or authorization
  4. Review LDAP filter configurations for user-facing input
    Examine the LDAP search filters configured in wkplcldap.properties or through the admin console to identify any points where user-supplied input could be passed into LDAP query parameters without proper escaping.
    Affected if User-provided parameters can be injected into LDAP search filters

A system is affected if it runs IBM WebSphere Portal version 6.1.0.0 through 8.5.0 and has LDAP configured as the user repository, enabling the LDAP injection vulnerability.

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

Apply the appropriate IBM WebSphere Portal Cumulative Fix (CF20 for 8.0.0.x, CF10 for 8.5.0, or later compatible CFs for earlier versions) to patch the LDAP injection vulnerability. Additionally, implement input validation on all user-supplied data that interfaces with LDAP directory queries.

Fix this in Websphere Portal Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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