CVE-2019-16214
Libra Core Regular Expression Injection
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.
INFO
Published Date :
Sept. 11, 2019, 4:15 a.m.
Last Modified :
Aug. 24, 2020, 5:37 p.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
3.6
Exploitability Score :
2.1
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2019-16214.
| URL | Resource |
|---|---|
| https://blog.openzeppelin.com/libra-vulnerability-release/ | Third Party Advisory |
| https://blog.openzeppelin.com/libra-vulnerability-summary/ | Exploit Third Party Advisory |
| https://github.com/libra/libra/commit/7efb0221989f17fdf7f8486730898ed947a1e19e | Patch Third Party Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2019-16214 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2019-16214 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
CWE Remap by [email protected]
Aug. 24, 2020
Action Type Old Value New Value Changed CWE CWE-20 NVD-CWE-noinfo -
Initial Analysis by [email protected]
Sep. 11, 2019
Action Type Old Value New Value Added CVSS V2 Metadata Victim must voluntarily interact with attack mechanism Added CVSS V2 NIST (AV:N/AC:M/Au:S/C:N/I:P/A:N) Added CVSS V3.1 NIST AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N Changed Reference Type https://blog.openzeppelin.com/libra-vulnerability-release/ No Types Assigned https://blog.openzeppelin.com/libra-vulnerability-release/ Third Party Advisory Changed Reference Type https://blog.openzeppelin.com/libra-vulnerability-summary/ No Types Assigned https://blog.openzeppelin.com/libra-vulnerability-summary/ Exploit, Third Party Advisory Changed Reference Type https://github.com/libra/libra/commit/7efb0221989f17fdf7f8486730898ed947a1e19e No Types Assigned https://github.com/libra/libra/commit/7efb0221989f17fdf7f8486730898ed947a1e19e Patch, Third Party Advisory Added CWE CWE-20 Added CPE Configuration OR *cpe:2.3:a:libra:libra_core:*:*:*:*:*:*:*:* versions up to (excluding) 2019-09-03
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2019-16214 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2019-16214
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.11 }} 0.03%
score
0.44513
percentile