# CVE-2014-6602: Auth bypass in n/a

> Physically proximate attackers can bypass the lock screen on Nokia Asha phones to read contacts or dial numbers via SOS menu interaction.

- **Severity:** Medium 6.6 (`AV:L/AC:L/Au:N/C:C/I:C/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-32c9-pf87-q237

## What is CVE-2014-6602?

CVE-2014-6602 is a medium-severity authentication bypass vulnerability in n/a, published on 22 Sep 2014. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Microsoft Asha OS on the Microsoft Mobile Nokia Asha 501 phone 14.0.4 allows physically proximate attackers to bypass the lock-screen protection mechanism, and read or modify contact information or dial arbitrary telephone numbers, by tapping the SOS Option and then tapping the Green Call Option.

Weakness: CWE-264

## Which versions are affected by CVE-2014-6602?

It affects 2 products.


Products: Microsoft Nokia Asha 501, Microsoft Nokia Asha 501 Software.

## How do I fix CVE-2014-6602?

No fix has been published for CVE-2014-6602 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-6602 being exploited?

There is no known exploitation of CVE-2014-6602 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-6602 and fix it if it is affected.

What it is: CVE-2014-6602 is a medium-severity authentication bypass vulnerability in n/a, published on 22 Sep 2014. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-6602 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-6602/ (Markdown: https://insights.sbomify.com/CVE-2014-6602/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-6602
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-6602
- OSV: https://osv.dev/vulnerability/CVE-2014-6602

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-6602/
Summaries are generated and may contain mistakes; the official description above is the record.