CVE-2012-1291
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 com.sap.aii.mdt.amt.web.AMTPageProcessor servlet in SAP NetWeaver 7.0 allows remote attackers to obtain sensitive information about the Adapter Monitor via unspecified vectors, possibly related to the EnableInvokerServletGlobally property in the servlet_jsp service.
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 confidenceThis is an information disclosure vulnerability in SAP NetWeaver 7.0's Adapter Monitor (AMT) servlet (com.sap.aii.mdt.amt.web.AMTPageProcessor). The vulnerability allows remote attackers to obtain sensitive information about the Adapter Monitor through unspecified vectors, likely due to improper configuration of the EnableInvokerServletGlobally property in the servlet_jsp service, which can expose the servlet to unauthorized 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= 7.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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify SAP NetWeaver versionCheck the installed SAP NetWeaver version using SAP Management Console, SAP MMC, or by querying the system properties. Look for version 7.0 specifically.Affected if The installed version is SAP NetWeaver 7.0 exactly.
-
Confirm AMT servlet is deployedLocate the Adapter Monitor (AMT) servlet (com.sap.aii.mdt.amt.web.AMTPageProcessor) in the SAP system. This may be visible in the servlet_jsp service configuration or through SAP's servlet registry.Affected if The AMTPageProcessor servlet is present in the deployment.
-
Check EnableInvokerServletGlobally propertyAccess the servlet_jsp service configuration in SAP NetWeaver Administrator or through SAP Management Console. Locate the EnableInvokerServletGlobally property and verify its current setting.Affected if EnableInvokerServletGlobally is set to enabled or true, making the servlet globally accessible.
-
Test servlet accessibilityAttempt to access the AMTPageProcessor servlet via HTTP/HTTPS from an unauthorized network location. Common paths include /servlet/com.sap.aii.mdt.amt.web.AMTPageProcessor or the mapped web module URL.Affected if The servlet responds and returns information without requiring authentication or proper authorization.
A user is affected if running SAP NetWeaver 7.0 with the EnableInvokerServletGlobally property enabled, allowing unauthorized access to the AMT servlet which discloses sensitive Adapter Monitor information.
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 dataDisable or properly secure the EnableInvokerServletGlobally property in the servlet_jsp service configuration and restrict access to the AMTPageProcessor servlet to prevent unauthorized information disclosure.
- Consultation4.0 h
- Implementation3.0 h
- Testing2.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 $3,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1291 — 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-1291 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