# CVE-2019-9865: Integer overflow in n/a

> Remote attackers can cause denial of service or execute arbitrary code via crafted RPC requests in VxWorks when RPC is enabled.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rjfr-98mq-vp3p

## What is CVE-2019-9865?

CVE-2019-9865 is a high-severity vulnerability in n/a, published on 29 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

When RPC is enabled in Wind River VxWorks 6.9 prior to 6.9.1, a specially crafted RPC request can trigger an integer overflow leading to an out-of-bounds memory copy. It may allow remote attackers to cause a denial of service (crash) or possibly execute arbitrary code.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2019-9865?

It affects 1 product.


Products: Windriver Vxworks.

## How do I fix CVE-2019-9865?

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

## Is CVE-2019-9865 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-0714](https://insights.sbomify.com/CVE-2013-0714/): Other in n/a (critical 10.0)
- [CVE-2021-29999](https://insights.sbomify.com/CVE-2021-29999/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-38346](https://insights.sbomify.com/CVE-2023-38346/): Path traversal in n/a (high 8.8)
- [CVE-2015-7599](https://insights.sbomify.com/CVE-2015-7599/): Integer overflow in n/a (high 8.1)
- [CVE-2013-0711](https://insights.sbomify.com/CVE-2013-0711/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9865 and fix it if it is affected.

What it is: CVE-2019-9865 is a high-severity vulnerability in n/a, published on 29 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-9865 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-2019-9865/ (Markdown: https://insights.sbomify.com/CVE-2019-9865/index.md)
```

## Sources

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

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