CVE-2012-0191
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 · uneditedThe web container in IBM Lotus Expeditor 6.1.x and 6.2.x before 6.2 FP5+Security Pack does not properly perform access control for requests, which allows remote attackers to spoof a localhost request origin via crafted headers.
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 confidenceThe web container in IBM Lotus Expeditor fails to properly validate request origins, allowing attackers to spoof localhost requests by manipulating HTTP headers. This enables attackers to bypass origin-based access controls by sending crafted requests that appear to originate from localhost.
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= 6.1= 6.1.1= 6.2= 6.2.1= 6.2.2= 6.2.3CVSS 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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.
-
Confirm IBM Lotus Expeditor installation and versionLocate the IBM Lotus Expeditor installation directory and check the version manifest or about dialog. Common locations include C:\Program Files\IBM\Lotus\Expeditor or /opt/IBM/Lotus/Expeditor. Look for version.info or about.properties files.Affected if The installed version is 6.1, 6.1.1, 6.2, 6.2.1, 6.2.2, or 6.2.3
-
Identify if web container component is enabledExamine the IBM Lotus Expeditor configuration to determine if the web container (HTTP server) feature is actively running. Check the configuration files in the workspace or configuration directory for web container plugin activation.Affected if The web container component is enabled and processing HTTP requests
-
Verify HTTP origin validation configurationInspect the web container configuration files for settings related to origin validation, host header validation, or request source validation. Look for properties controlling X-Forwarded-Host, Host header, or similar HTTP header checks.Affected if Origin validation is not properly enforced or can be bypassed via header manipulation
-
Check for localhost access control rulesReview the access control lists or security constraints configured for the web container that rely on localhost or origin-based restrictions. Determine if these controls can be circumvented by manipulating HTTP headers.Affected if Access controls depend on origin/host headers without proper validation
A user is affected if IBM Lotus Expeditor version 6.1.x or 6.2.x through 6.2.3 is installed with the web container enabled and the environment relies on origin-based access controls that can be bypassed via HTTP header manipulation.
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 IBM Lotus Expeditor to version 6.2 FP5+Security Pack or later, which contains the proper access control validation for request origins.
- Consultation3.0 h
- Implementation4.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0191 — 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-0191 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