Vulnerability Details : CVE-2019-16096
Kilo 0.0.1 has a heap-based buffer overflow because there is an integer overflow in a calculation involving the number of tabs in one row.
Vulnerability category: OverflowMemory Corruption
Products affected by CVE-2019-16096
- cpe:2.3:a:kilo_project:kilo:0.0.1:*:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2019-16096
0.29%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 70 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2019-16096
Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
---|---|---|---|---|---|---|
5.0
|
MEDIUM | AV:N/AC:L/Au:N/C:N/I:N/A:P |
10.0
|
2.9
|
NIST | |
7.5
|
HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
3.9
|
3.6
|
NIST |
CWE ids for CVE-2019-16096
-
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.Assigned by: nvd@nist.gov (Primary)
-
The product writes data past the end, or before the beginning, of the intended buffer.Assigned by: nvd@nist.gov (Primary)
References for CVE-2019-16096
-
https://vuldb.com/?id.141388
Kilo 0.0.1 Tab Integer Overflow memory corruptionThird Party Advisory
-
https://github.com/antirez/kilo/issues/60
Integer Overflow && heap-buffer-overflow in kilo.c · Issue #60 · antirez/kilo · GitHubExploit;Issue Tracking
-
https://vulmon.com/vulnerabilitydetails?qid=CVE-2019-16096
CVE-2019-16096 Kilo 0.0.1 has a heap-based buffer overflow bec...Issue Tracking
-
http://www.security-database.com/detail.php?alert=CVE-2019-16096
CVE-2019-16096 - Alert Detail - Security DatabaseThird Party Advisory
Jump to