Published: 18/10/2019 Updated: 16/02/2024

CVSS v2 Base Score: 10 | Impact Score: 10 | Exploitability Score: 10

CVSS v3 Base Score: 9.8 | Impact Score: 5.9 | Exploitability Score: 3.9

VMScore: 891

Vector: AV:N/AC:L/Au:N/C:C/I:C/A:C

An issue exists in slicer69 doas prior to 6.2 on certain platforms other than OpenBSD. On platforms without strtonum(3), sscanf was used without checking for error cases. Instead, the uninitialized variable errstr was checked and in some cases returned success even if sscanf failed. The result was that, instead of reporting that the supplied username or group name did not exist, it would execute the command as root.

Vulnerable Product	Search on Vulmon	Subscribe to Product
doas project doas

Uninitialized variable vulnerability - Problem with boolean variables that are forcibly initialized to false by the Java compiler Sites such as CWE and VULNCAT all describe only code quality and memory problems, so I made an example code for the vulnerability of an uninitialized variable(1) In the Java language, boolean member variables that are not explicitly initialized are

CWE-754 CWE-252 CWE-863 CWE-908 https://github.com/slicer69/doas/compare/6.1p1...6.2 https://github.com/slicer69/doas/commit/2f83222829448e5bc4c9391d607ec265a1e06531 https://nvd.nist.gov https://github.com/windshock/Missing-Initialization-of-a-Variable

CVE-2019-15900

Vulnerability Summary

Vulnerability Trend

Github Repositories

References

Vulmon Search

About

Products

Connect