dbcve.org
Rational AppscanApplication · Ibm

CVE-2011-1367

HIGH · 9.3 CVSS v2.0 Published 2011-10-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Unspecified vulnerability in the File Load feature in IBM Rational AppScan Standard and Express 7.8.x, 7.9.x, and 8.0.x before 8.0.0.3 allows remote attackers to execute arbitrary commands via a crafted .scan 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

IBM Rational AppScan (versions 7.8.x, 7.9.x, and 8.0.x before 8.0.0.3) contains an unspecified vulnerability in its File Load feature. Attackers can craft malicious .scan files that, when opened by a user, allow arbitrary command execution on the target system.

MitigationUpgrade IBM Rational AppScan to version 8.0.0.3 or later. If upgrade is not possible, exercise extreme caution when opening .scan files from untrusted sources and consider disabling the File Load feature until patched.

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
Rational AppscanApplication
Affected:= 7.8.0= 7.8.0.1= 7.8.0.2= 7.9.0= 7.9.0.1= 7.9.0.2= 7.9.0.3= 8.0.0= 8.0.0.1= 8.0.0.2

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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/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. Verify IBM Rational AppScan is installed
    Check for the presence of IBM Rational AppScan in the program directory (commonly at C:\Program Files\IBM\Rational\AppScan or C:\Program Files (x86)\IBM\Rational\AppScan) or look for the application in the Windows Start Menu under IBM Rational AppScan.
    Affected if IBM Rational AppScan is present on the system.
  2. Determine the installed version number
    Open IBM Rational AppScan and navigate to Help > About, or right-click the appscan.exe file, select Properties, and check the Version tab. Record the exact version number (for example, 8.0.0.2, 7.9.0.3, or 7.8.0.2).
    Affected if The installed version is 7.8.0, 7.8.0.1, 7.8.0.2, 7.9.0, 7.9.0.1, 7.9.0.2, 7.9.0.3, 8.0.0, 8.0.0.1, or 8.0.0.2.
  3. Confirm access to the File Load feature
    In the IBM Rational AppScan interface, locate the File menu or toolbar. Look for a 'File Load', 'Load Scan', or similar option that allows opening .scan files. This feature is present in all standard installations of the affected versions.
    Affected if The File Load or Open function for .scan files is accessible in the application.
  4. Identify recently opened .scan files
    Check the application's recent files list (File > Recent Scans) or examine the file system for .scan files that may have been opened from untrusted sources. Inspect the Windows Temp folder or Downloads folder for any .scan files of unknown origin.
    Affected if Any .scan file from an untrusted source has been opened using the File Load feature.

A user is affected if IBM Rational AppScan versions 7.8.0 through 8.0.0.2 are installed and the File Load feature is used to open .scan files, allowing arbitrary command execution through maliciously crafted files.

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

Upgrade IBM Rational AppScan to version 8.0.0.3 or later. If upgrade is not possible, exercise extreme caution when opening .scan files from untrusted sources and consider disabling the File Load feature until patched.

Recommended fix Moderate confidence

Rational AppScan Standard/Express 8.0.0.3 or later

  1. 1. Verify current IBM Rational AppScan installation version via Help > About in the application
  2. 2. If version is 7.8.0, 7.8.0.1, 7.8.0.2, 7.9.0, or any 8.0.x version before 8.0.0.3, download Rational AppScan Standard or Express version 8.0.0.3 or later from IBM Fix Central (https://www-01.ibm.com/support/fixcentral/)
  3. 3. Ensure all .scan files are from trusted sources pending upgrade, as the vulnerability is exploited via malicious .scan files
  4. 4. Install the upgraded version following IBM's standard installation procedures
  5. 5. After upgrade, verify the File Load feature functions correctly with legitimate .scan files
Caveat Users should test existing scan configurations and custom templates with the new version before production deployment, as minor UI or workflow changes may exist between major versions

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

Fix this in Rational Appscan Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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