# CVE-2024-49408: Memory corruption in Samsung Mobile Devices

> Local attackers with system privileges can trigger an out-of-bounds write in the USB driver, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Nov 2024
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-g36j-7gxf-23fw

## What is CVE-2024-49408?

CVE-2024-49408 is a medium-severity memory corruption vulnerability in Samsung Mobile Devices, published on 6 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Out-of-bounds write in usb driver prior to Firmware update Sep-2024 Release on Galaxy S24 allows local attackers to write out-of-bounds memory. System privilege is required for triggering this vulnerability.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2024-49408?

It affects 1 product.


Products: Samsung Galaxy S24 Firmware.

## How do I fix CVE-2024-49408?

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

## Is CVE-2024-49408 being exploited?

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

## Other vulnerabilities in Samsung Mobile Devices

- [CVE-2024-49409](https://insights.sbomify.com/CVE-2024-49409/): Memory corruption in Samsung Mobile Devices (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-49408 and fix it if it is affected.

What it is: CVE-2024-49408 is a medium-severity memory corruption vulnerability in Samsung Mobile Devices, published on 6 Nov 2024. 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-2024-49408 in the wild and no public exploit code.

Affected product: Samsung Mobile Devices. 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-2024-49408/ (Markdown: https://insights.sbomify.com/CVE-2024-49408/index.md)
```

## Sources

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

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