# CVE-2023-30024: Privilege escalation in n/a

> Attackers can exploit hidden NAND partitions to replace firmware, enabling ransomware deployment on the host computer.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 28 Apr 2023
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-f842-4gqm-2cpg

## What is CVE-2023-30024?

CVE-2023-30024 is a medium-severity vulnerability in n/a, published on 28 Apr 2023. 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

The MagicJack device, a VoIP solution for internet phone calls, contains a hidden NAND flash memory partition allowing unauthorized read/write access. Attackers can exploit this by replacing the original software with a malicious version, leading to ransomware deployment on the host computer. Affected devices have firmware versions prior to magicJack A921 USB Phone Jack Rev 3.0 V1.4.

Weakness: CWE-269 (Improper Privilege Management), CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2023-30024?

It affects 1 product.


Products: Magicjack A921 Firmware.

## How do I fix CVE-2023-30024?

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

## Is CVE-2023-30024 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-30024 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-30024 and fix it if it is affected.

What it is: CVE-2023-30024 is a medium-severity vulnerability in n/a, published on 28 Apr 2023. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-30024 exists.

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-2023-30024/ (Markdown: https://insights.sbomify.com/CVE-2023-30024/index.md)
```

## Sources

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

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