# CVE-2013-4877: Auth bypass in n/a

> Remote attackers can sniff registration packets to steal ESN and MIN values, enabling phone cloning attacks on Verizon Network Extenders.

- **Severity:** Low 2.6 (`AV:L/AC:H/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p7rg-rp2h-c9h8

## What is CVE-2013-4877?

CVE-2013-4877 is a low-severity authentication bypass vulnerability in n/a, published on 18 Jul 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Verizon Wireless Network Extender SCS-26UC4 and SCS-2U01 does not use CAVE authentication, which makes it easier for remote attackers to obtain ESN and MIN values from arbitrary phones, and conduct cloning attacks, by sniffing the network for registration packets.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2013-4877?

It affects 1 product.


Products: Verizon Wireless Network Extender.

## How do I fix CVE-2013-4877?

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

## Is CVE-2013-4877 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4874](https://insights.sbomify.com/CVE-2013-4874/): Auth bypass in n/a (medium 6.2)
- [CVE-2013-4875](https://insights.sbomify.com/CVE-2013-4875/): Auth bypass in n/a (medium 6.2)
- [CVE-2013-4876](https://insights.sbomify.com/CVE-2013-4876/): Hardcoded credentials in n/a (medium 6.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4877 and fix it if it is affected.

What it is: CVE-2013-4877 is a low-severity authentication bypass vulnerability in n/a, published on 18 Jul 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4877 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-2013-4877/ (Markdown: https://insights.sbomify.com/CVE-2013-4877/index.md)
```

## Sources

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

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