# CVE-2014-1909: Integer overflow in n/a

> A signedness error in Android Debug Bridge allows malicious servers to execute arbitrary code via stack-based buffer overflow.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-1909, GHSA-58c5-6h84-hwh5, openSUSE-SU-2024:10324-1

## What is CVE-2014-1909?

CVE-2014-1909 is a high-severity vulnerability in Opensuse Opensuse, published on 14 May 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Integer signedness error in system/core/adb/adb_client.c in Android Debug Bridge (ADB) for Android 4.4 in the Android SDK Platform Tools 18.0.1 allows ADB servers to execute arbitrary code via a negative length value, which bypasses a signed comparison and triggers a stack-based buffer overflow.

Weakness: CWE-189

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

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `android-tools` | openSUSE:Tumbleweed | All versions | 5.1.1_r8-3.5 |

Products: Google Android Debug Bridge, Google Android Sdk Platform Tools, Opensuse Opensuse.

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

Upgrade to a fixed version.

## Is CVE-2014-1909 being exploited?

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

## Other vulnerabilities in Opensuse Opensuse

- [CVE-2012-5564](https://insights.sbomify.com/CVE-2012-5564/): Path traversal in n/a (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-1909 is a high-severity vulnerability in Opensuse Opensuse, published on 14 May 2014. 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-2014-1909 in the wild and no public exploit code.

Affected product: Opensuse Opensuse. 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-1909/ (Markdown: https://insights.sbomify.com/CVE-2014-1909/index.md)
```

## Sources

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

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