CVE-2011-1104
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 · uneditedMultiple cross-site request forgery (CSRF) vulnerabilities in Mutare EVM allow remote attackers to hijack the authentication of arbitrary users for requests that (1) change a PIN, (2) delete messages, (3) add a delivery address, or (4) change a delivery address.
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 confidenceMutare EVM contains multiple CSRF vulnerabilities allowing remote attackers to hijack authenticated user sessions for state-changing operations including PIN changes, message deletion, and delivery address modifications.
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 dataall versionsCVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/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.
-
Confirm Mutare EVM presenceIdentify whether Mutare EVM software is installed in your environment through installed software lists, web application enumeration, or system inventory documentation.Affected if Mutare EVM is found in your environment
-
Locate state-changing functionsAccess the Mutare EVM interface and navigate to the areas that handle PIN changes, message deletion, and delivery address modifications.Affected if These authenticated state-changing features are accessible
-
Inspect PIN change form for CSRF protectionExamine the HTML source or network requests for the PIN change functionality. Check for the presence of a unique anti-CSRF token (synchronizer token) as a hidden form field or custom header.Affected if The PIN change form lacks an anti-CSRF token or uses predictable/constant token values
-
Inspect message deletion for CSRF protectionExamine the HTML source or network requests for message deletion operations. Verify that each deletion request includes a unique, unpredictable token.Affected if Message deletion lacks anti-CSRF token protection
-
Inspect delivery address modification for CSRF protectionExamine the HTML source or network requests for delivery address modification features. Check for the presence of anti-CSRF tokens in the request.Affected if Address modification lacks anti-CSRF token protection
If Mutare EVM is installed and any of its state-changing operations (PIN changes, message deletion, or address modifications) lack anti-CSRF token protection, the environment is affected by CVE-2011-1104.
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 dataImplement anti-CSRF tokens (synchronizer token pattern) for all state-changing operations and validate Origin/Referer headers to prevent cross-site request forgery attacks.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1104 — 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-1104 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