CVE-2012-0729
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 · uneditedUnrestricted file upload vulnerability in IBM Rational AppScan Enterprise 5.x and 8.x before 8.5.0.1 allows remote authenticated users to execute arbitrary ASP.NET code by uploading a .aspx file, and then accessing it 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 confidenceUnrestricted file upload vulnerability in IBM Rational AppScan Enterprise versions 5.x and 8.x before 8.5.0.1 allows authenticated remote users to upload malicious .aspx files containing arbitrary ASP.NET code, which can then be executed on the server via web access.
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.0= 5.5.0.1= 5.5.0.2= 5.6.0= 5.6.0.3= 8.0.0= 8.0.0.1= 8.0.0.2= 8.0.0.3= 8.0.1CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:S/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 checksWork through these to decide whether this CVE applies to you.
-
Identify IBM Rational AppScan Enterprise installationLocate the AppScan Enterprise installation directory. Common paths include C:\Program Files\IBM\Rational AppScan\ or C:\IBM\Rational AppScan\ on Windows. Check for the presence of the main application executable (AppScanEnterpriseConsole.exe or similar).Affected if IBM Rational AppScan Enterprise is installed on the system.
-
Determine installed versionOpen the IBM Rational AppScan Enterprise console or check the program files for version information. The version is typically displayed in the About section of the application or can be found in the installation directory metadata.Affected if The installed version matches any of the following: 5.2, 5.4, 5.5.0, 5.5.0.1, 5.5.0.2, 5.6.0, 5.6.0.3, 8.0.0, 8.0.0.1, 8.0.0.2, 8.0.0.3, or 8.0.1.
-
Verify file upload functionalityCheck if the AppScan Enterprise web interface includes upload functionality. This typically involves accessing the Scan Configuration or Task upload features through the web portal.Affected if The application allows file uploads through its web interface and the user has authenticated access.
-
Inspect upload storage locationExamine the web server configuration to determine where uploaded files are stored. In IIS, check the web.config or the physical directory referenced by the upload endpoint.Affected if Uploaded files are stored within the web root directory structure where .aspx files can be executed.
-
Test .aspx file upload capabilityAttempt to upload a test .aspx file through the application's upload feature, if authorized in a non-production test environment. Then attempt to access the uploaded file via web browser.Affected if The application accepts .aspx file uploads and serves them from a location where ASP.NET code can be executed.
The environment is affected if IBM Rational AppScan Enterprise versions 5.2 through 8.0.0.3 or 8.0.1 are installed and the application allows uploading .aspx files to a web-accessible location.
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 IBM Rational AppScan Enterprise 8.5.0.1 or later. Additionally, implement strict file type validation on upload endpoints and store user uploads outside the web root to prevent execution.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0729 — 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-2012-0729 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