CVE-2011-1472
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 Nokia E75 phone with firmware before 211.12.01 allows physically proximate attackers to bypass the Device Lock code by entering an unspecified button sequence at boot time.
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 Nokia E75 phone contains a security flaw in firmware versions prior to 211.12.01 where a physically proximate attacker can bypass the Device Lock code by entering a specific button sequence during the boot process, allowing unauthorized access to the device without knowing the actual lock code.
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<= 211.12= 210.12.15all 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/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 the device modelCheck the physical phone or device settings to confirm the model is Nokia E75. This can be done by looking at the device label, packaging, or checking Settings > About > Device name.Affected if The device is not a Nokia E75 model, then this specific CVE does not apply.
-
Check the installed firmware versionOn the Nokia E75, dial *#0000# to display the firmware version, or go to Settings > About > Device info to view the current firmware version installed on the device.Affected if The firmware version cannot be determined or the device does not support version checking.
-
Compare firmware version against affected rangesExamine the firmware version displayed in the previous step. The affected versions are any version <= 211.12 or exactly version 210.12.15. Note that version 211.12.01 is the patched release.Affected if The installed firmware version is 211.12.15 or lower, or is exactly 210.12.15.
-
Verify the Device Lock security featureConfirm that the Device Lock code feature is enabled on the phone. Go to Settings > Security > Device lock to verify the lock is active. The vulnerability only affects devices where Device Lock is configured.Affected if The Device Lock code is enabled and the firmware version falls within the affected ranges.
A user is affected if they are using a Nokia E75 with firmware version 211.12.15 or lower (or exactly 210.12.15) and have the Device Lock security feature enabled.
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 dataUpdate Nokia E75 firmware to version 211.12.01 or later to patch the button sequence bypass vulnerability. Maintain physical control of devices to prevent unauthorized access.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1472 — 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-1472 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