Skip to main content
Mallory
← Back to News
identity-authentication-vulnerabilityembedded-device-vulnerabilityproof-of-concept-release

OpenBSD PPP PAP Flaw Allowed Authentication Bypass Across All Releases

Vulnerability Disclosure · 7 sources · Updated 5mo ago · First seen Jun 16, 2026

OpenBSD PPP PAP Flaw Allowed Authentication Bypass Across All Releases

OpenBSD fixed a high-severity authentication bypass in its PPP stack after researchers disclosed that the bug had existed since the original sppp code import from FreeBSD in 1999. The flaw affects sppp_pap_input() and all OpenBSD releases through 7.6 when the system is configured as a PAP authenticator on the PPPoE data path. By trusting attacker-controlled name_len and passwd_len values in bcmp() comparisons, the code could accept zero-length credentials as valid because a zero-length bcmp() returns success, allowing remote attackers to authenticate without legitimate credentials.

The disclosure also described a secondary kernel heap over-read caused when a supplied username length exceeds the allocated size of the stored credential, a condition introduced after credential fields became dynamically allocated in 2009. Researchers said the bug could let an attacker intercept or read PPPoE traffic and could also allow a rogue PPPoE server to impersonate a legitimate server during mutual authentication. OpenBSD committed a fix to -current on 2026-06-14, and a proof of concept reportedly showed successful PAP authentication with empty credentials followed by establishment of a full network-layer link.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

4 events · Jul 1, 1999 – Jun 14, 2026
  1. Jun 14, 20265mo ago

    OpenBSD commits fix for PAP authentication bypass

    OpenBSD committed a fix to -current for the high-severity sppp_pap_input() authentication bypass on 2026-06-14. The flaw affected all versions through 7.6 and allowed zero-length credentials to authenticate successfully due to attacker-controlled length values being used in bcmp() comparisons.

    oss-sec: OpenBSD sppp_pap_input: PAP authentication bypass
  2. Jul 1, 199927y ago

    Vulnerability disclosure details PAP bypass and PoC

    The vulnerability was publicly disclosed with technical details describing the PAP null-auth weakness, affected OpenBSD versions, PPPoE reachability, and a Python proof of concept that successfully authenticated with empty credentials and established a network-layer link.

    oss-sec: OpenBSD sppp_pap_input: PAP authentication bypass
  3. Jul 1, 199927y ago

    2009 change enables secondary kernel heap over-read

    A 2009 change that moved credential fields to dynamic allocation enabled a secondary kernel heap over-read condition in the same code path when a supplied PAP name length exceeded the allocated stored credential size.

    oss-sec: OpenBSD sppp_pap_input: PAP authentication bypass
  4. Jul 1, 199927y ago

    OpenBSD imports vulnerable sppp code from FreeBSD

    The vulnerable comparison pattern in OpenBSD's PPP stack originated when sppp code was imported from FreeBSD in July 1999, introducing the PAP authentication bypass condition.

    27 Years in the Dark: OpenBSD Fixes Ancient Remote Kernel Auth Bypass : r/netsec
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

1 linked
Openbsd
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.