Libra Core
Approved changes feed: RSS · Atom
cpe:2.3:a:libra:libra_core:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Libra (34227caf-55e4-5aac-b2c0-ee25a8f3af01) |
|---|---|
| Product | Libra Core (316586c6-7586-5d4a-a145-8753b02d9d30) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/diem/diem |
purl2cpe | 2026-06-01 10:17:41.589677 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2019-16214 |
vulnerable | 2026-06-08 05:13:07.911716 |
Details available
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.
Published: 2019-09-11T03:51:57.000Z
Updated: 2024-08-05T01:10:41.445Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.