# CVE-2018-20999: Flaw in streaming state in orion


- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 26 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gffv-5hr2-f9gj, RUSTSEC-2018-0012

## What is CVE-2018-20999?

CVE-2018-20999 is a high-severity vulnerability in n/a, published on 26 Aug 2019. 

### Official description

An issue was discovered in the orion crate before 0.11.2 for Rust. reset() calls cause incorrect results.

Weakness: CWE-682 (Incorrect Calculation)

## Which versions are affected by CVE-2018-20999?

3 open source packages ship an affected version, including orion. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `orion` | crates.io | All versions | 0.11.2 |
| `orion` | crates.io | All versions | 0.11.2 |
| `orion` | crates.io | From 0.0.0-0 | 0.11.2 |

Products: Orion Project Orion.

## How do I fix CVE-2018-20999?

Upgrade orion to 0.11.2 or later.

## Is CVE-2018-20999 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20999 and fix it if it is affected.

What it is: CVE-2018-20999 is a high-severity vulnerability in n/a, published on 26 Aug 2019. 
Exploitation: There is no known exploitation of CVE-2018-20999 in the wild and no public exploit code.

Affected packages and fixed versions:
- orion (crates.io): affected all versions; fixed in 0.11.2
- orion (crates.io): affected all versions; fixed in 0.11.2
- orion (crates.io): affected from 0.0.0-0; fixed in 0.11.2

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

## Sources

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

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