Facebook Libra Core Inline Comment parser.rs input validation
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
5.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Facebook Libra Core. It has been rated as critical. Affected by this issue is some unknown functionality of the file language/compiler/ir_to_bytecode/src/parser.rs of the component Inline Comment Handler. The manipulation leads to input validation. This vulnerability is handled as CVE-2019-16214. The attack may be launched remotely. There is no exploit available. It is recommended to upgrade the affected component. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability was found in Facebook Libra Core (Social Network Software) (unknown version). It has been declared as critical. Affected by this vulnerability is an unknown code block of the file language/compiler/ir_to_bytecode/src/parser.rs of the component Inline Comment Handler. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was shared 09/11/2019. This vulnerability is known as CVE-2019-16214 since 09/10/2019. The exploitation appears to be difficult. The attack can be launched remotely. The requirement for exploitation is a single authentication. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.1VulDB Meta Temp Score: 5.0
VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.7
NVD Vector: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
09/03/2019 🔍09/10/2019 🔍
09/11/2019 🔍
09/11/2019 🔍
12/19/2023 🔍
Sources
Advisory: 7efb0221989f17fdf7f8486730898ed947a1e19eStatus: Not defined
CVE: CVE-2019-16214 (🔍)
GCVE (CVE): GCVE-0-2019-16214
GCVE (VulDB): GCVE-100-141559
Entry
Created: 09/11/2019 08:46 AMUpdated: 12/19/2023 09:30 AM
Changes: 09/11/2019 08:46 AM (37), 08/19/2020 09:55 AM (18), 12/19/2023 09:30 AM (6)
Complete: 🔍
Cache ID: 18:5C4:40
No comments yet. Languages: en.
Please log in to comment.