CVE-2011-1366
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 · uneditedUnspecified vulnerability in the Import feature in IBM Rational AppScan Enterprise and AppScan Reporting Console 5.2 through 7.9.x and 8.x before 8.0.1.1 allows remote attackers to execute arbitrary commands on an agent server via a crafted ZIP archive.
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 confidenceArbitrary command execution vulnerability in IBM Rational AppScan Enterprise and AppScan Reporting Console's Import feature allows remote attackers to execute commands on the agent server via a crafted ZIP archive. This is a classic file upload/code injection flaw where unsanitized archive processing leads to OS command execution.
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= 5.2= 5.4= 5.5= 5.5.0= 5.5.0.1= 5.5.0.2= 5.6.0= 5.6.0.3= 7.7.0= 7.7.0.1= 7.7.0.2= 7.8.0CVSS 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
- None
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed IBM Rational AppScan productCheck the installed programs on the system for 'IBM Rational AppScan Enterprise' or 'IBM Rational AppScan Reporting Console'. Check installation directories such as C:\Program Files\IBM\Rational\AppScan or look for AppScan services running on the system.Affected if The product is installed and is one of the affected versions.
-
Determine the exact version numberLocate the version information in the product's About dialog, installation logs, or registry entries under HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Rational AppScan. Compare this version against the affected list: 5.2, 5.4, 5.5, 5.5.0, 5.5.0.1, 5.5.0.2, 5.6.0, 5.6.0.3, 7.7.0, 7.7.0.1, 7.7.0.2, 7.8.0.Affected if The installed version exactly matches one of the versions in the affected list.
-
Verify the Import feature is accessibleCheck if the Import functionality in the AppScan web interface (typically at /Import or /ase/import) is exposed and accessible. Review the application configuration to confirm the Import module is enabled.Affected if The Import feature is enabled and network-accessible, making it a potential attack vector.
-
Inspect for signs of exploitationReview web server logs and application logs for suspicious requests to the Import endpoint, particularly those containing .zip file uploads with unusual file names or paths. Check for new or unexpected files in the AppScan installation directory or web root.Affected if Log evidence shows suspicious Import requests or unexpected files indicating command injection attempts.
You are affected if IBM Rational AppScan Enterprise or AppScan Reporting Console is installed with a version matching 5.2 through 7.8.0 and the Import feature is accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to version 8.0.1.1 or later. Until patched, restrict network access to the Import feature and consider disabling it if possible.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1366 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-1366 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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