# CVE-2019-16214: Other in n/a

> Libra Core's parser mishandles carriage returns in comments, allowing code to be hidden from auditors while remaining executable, bypassing security reviews.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r66w-gh88-5cgc

## What is CVE-2019-16214?

CVE-2019-16214 is a medium-severity vulnerability in n/a, published on 11 Sep 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Libra Core before 2019-09-03 has an erroneous regular expression for inline comments, which makes it easier for attackers to interfere with code auditing by using a nonstandard line-break character for a comment. For example, a Move module author can enter the // sequence (which introduces a single-line comment), followed by very brief comment text, the \r character, and code that has security-critical functionality. In many popular environments, this code is displayed on a separate line, and thus a reader may infer that the code is executed. However, the code is NOT executed, because language/compiler/ir_to_bytecode/src/parser.rs allows the comment to continue after the \r character.

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

It affects 1 product.


Products: Libra Libra Core.

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

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

## Is CVE-2019-16214 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16214 is a medium-severity vulnerability in n/a, published on 11 Sep 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-16214 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-16214/ (Markdown: https://insights.sbomify.com/CVE-2019-16214/index.md)
```

## Sources

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

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