Amlogic pppoe_wrapper Command Injection via AF_UNIX Socket
Affects Nexbox A95X TV boxes (Amlogic S905/S905X) running the Amlogic Android SDK pppoe_wrapper daemon, in builds up to NEXBOX-A95X-201606011847 and NEXBOX-A95X-AP6330. No fix is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- Proof of concept public, per CISA
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Nexbox A95X (Amlogic S905/S905X) TV box running the Amlogic Android SDK pppoe_wrapper daemon Affected builds include A95X up to NEXBOX-A95X-201606011847 and NEXBOX-A95X-AP6330 The message must begin with the literal 'pppd pty'
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 35/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
The pppoe_wrapper daemon in Amlogic Android SDK builds, as shipped on Nexbox A95X (Amlogic S905/S905X) TV boxes, can be abused by a local user to run arbitrary commands with root privileges. This gives an attacker full control over the device.
Read the original description
The pppoe_wrapper vendor daemon from the Amlogic Android SDK, as shipped on Nexbox A95X (Amlogic S905/S905X) TV boxes, contains a command injection vulnerability that allows local attackers to execute arbitrary commands as root by sending crafted messages to a world-writable AF_UNIX datagram socket at /dev/socket/pppoe_wrapper. Attackers can send a message beginning with 'pppd pty' followed by shell metacharacters and arbitrary commands, which are passed unfiltered to system(3) and executed by /system/bin/sh -c as root, resulting in full privilege escalation.
What to do
Check whether your setup matches what the bug needs.
Nexbox A95X (Amlogic S905/S905X) TV box running the Amlogic Android SDK pppoe_wrapper daemon Affected builds include A95X up to NEXBOX-A95X-201606011847 and NEXBOX-A95X-AP6330 The message must begin with the literal 'pppd pty'Workaround: The checked facts do not include a workaround. No mitigation is listed for builds without a fix.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Nexbox A95X
NEXBOX-A95X-201606011847, NEXBOX-A95X-AP6330
- Amlogic Amlogic Android SDK
0
Evidence 2
- Exploit
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-119737
What does this mean?
The pppoe_wrapper daemon accepts messages over a local AF_UNIX socket. A local attacker can send a message beginning with 'pppd pty' and run arbitrary commands as root, which gives full privilege escalation.Source: vulncheck.com
Am I affected, and how do I check?
The bug affects Nexbox A95X (Amlogic S905/S905X) TV boxes running the Amlogic Android SDK pppoe_wrapper daemon. Affected builds include A95X up to NEXBOX-A95X-201606011847 and NEXBOX-A95X-AP6330. Compare the device's build identifier against these builds to see where it falls.Source: vulncheck.com
What should I do about it?
The checked facts do not name a fixed build or upgrade target. Check the vendor's update channel for a build newer than the affected listings.Source: vulncheck.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The checked facts do not include a workaround. No mitigation is listed for builds without a fix.Source: vulncheck.com