dbcve.org
Security AppscanApplication · Ibm

CVE-2013-0532

MEDIUM · 6.8 CVSS v2.0 Published 2013-03-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/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
Cross-site request forgery (CSRF) vulnerability in IBM Security AppScan Enterprise 5.6 and 8.x before 8.7 and IBM Rational Policy Tester 5.6 and 8.x before 8.5.0.4 allows remote attackers to hijack the authentication of arbitrary users for requests that cause a denial of service via malformed HTTP data.

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 · moderate confidence

CSRF vulnerability in IBM Security AppScan Enterprise (versions 5.6 and 8.x before 8.7) and IBM Rational Policy Tester (versions 5.6 and 8.x before 8.5.0.4) allows remote attackers to hijack authenticated user sessions and send malformed HTTP requests that trigger denial of service conditions.

MitigationApply vendor patches: upgrade AppScan Enterprise to version 8.7 or later, and Rational Policy Tester to version 8.5.0.4 or later. Additionally, implement anti-CSRF tokens and validate Origin/Referer headers as defense-in-depth measures.

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:= 5.6.0.0= 8.0.0.0= 8.0.0.1= 8.0.0.2= 8.0.1.0= 8.0.1.1= 8.0.11= 8.5.0.0= 8.5.0.1= 8.6.0.0= 8.6.0.1= 8.6.0.2
Rational Policy TesterApplication
Affected:= 5.6.0.0= 8.0.0.0= 8.0.0.1= 8.0.0.2= 8.0.1.0= 8.0.1.1= 8.5.0.0= 8.5.0.1= 8.5.0.2= 8.5.0.3

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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 IBM product
    Locate IBM Security AppScan Enterprise or IBM Rational Policy Tester installation. Check for installation directories (typically under C:\Program Files\IBM\ or /opt/IBM/), or use system inventory tools to list installed IBM software.
    Affected if Either IBM Security AppScan Enterprise or IBM Rational Policy Tester is installed on the system
  2. Retrieve AppScan Enterprise version
    Open Windows Programs and Features or Unix package manager. For AppScan Enterprise, also check the About section in the web console (typically https://hostname:8443/ase/), or check version info in installation directory files such as installer.properties or version.txt.
    Affected if The installed version matches 5.6.0.0, 8.0.0.0, 8.0.0.1, 8.0.0.2, 8.0.1.0, 8.0.1.1, 8.0.11, 8.5.0.0, 8.5.0.1, 8.6.0.0, 8.6.0.1, or 8.6.0.2 (any version before 8.7)
  3. Retrieve Rational Policy Tester version
    Open Windows Programs and Features or Unix package manager. Check version info in installation directory or in the Rational Policy Tester web interface About section.
    Affected if The installed version matches 5.6.0.0, 8.0.0.0, 8.0.0.1, 8.0.0.2, 8.0.1.0, 8.0.1.1, 8.5.0.0, 8.5.0.1, 8.5.0.2, or 8.5.0.3 (any version before 8.5.0.4)
  4. Confirm web interface accessibility
    Verify that the product web interface is network-accessible. For AppScan Enterprise, check ports 8443 or 8080. For Rational Policy Tester, check the configured HTTP/HTTPS ports.
    Affected if The web interface is exposed and the product version falls within the affected ranges

If IBM Security AppScan Enterprise version 8.6.2 or earlier, or IBM Rational Policy Tester version 8.5.0.3 or earlier is installed with an accessible web interface, the environment is affected by this CSRF 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 vendor patches: upgrade AppScan Enterprise to version 8.7 or later, and Rational Policy Tester to version 8.5.0.4 or later. Additionally, implement anti-CSRF tokens and validate Origin/Referer headers as defense-in-depth measures.

Fix this in Security Appscan Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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 locally
dbcve dependency scanner

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