VYPR
Unrated severityNVD Advisory· Published Feb 26, 1999· Updated Apr 16, 2026

CVE-1999-0381

CVE-1999-0381

Description

A buffer overflow in the syslog utility of super versions prior to 3.11.6 allows local users to gain root privileges.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A buffer overflow in the syslog utility of super versions prior to 3.11.6 allows local users to gain root privileges.

Vulnerability

A buffer overflow vulnerability exists in the syslog utility of super versions 3.11.6 and earlier. This issue occurs in the Error() function within error.c where a buffer named buf[MAXPRINT] is used without proper bounds checking. The syslog option must be enabled for this vulnerability to be present [1].

Exploitation

An attacker with local access can exploit this vulnerability. The SUPER program must be compiled with the SYSLOG option enabled. The exploit involves overwriting a buffer to gain control of the instruction pointer, allowing the attacker to execute arbitrary code. The provided exploit code creates a SUID bash shell owned by root at /tmp/sh [1].

Impact

Successful exploitation of this vulnerability allows a local user to gain root privileges on the affected system. This means the attacker can achieve complete control over the machine, including the ability to read, modify, or delete any file, and execute any command with the highest level of privilege [1].

Mitigation

No specific patched version is mentioned in the available references. However, the vulnerability is known to affect super versions 3.11.6 and earlier. Users are advised to upgrade to a version that addresses this vulnerability if available. Workarounds or further mitigation details are not yet disclosed in the available references [1].

AI Insight generated on Jun 2, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

2

News mentions

0

No linked articles in our index yet.