LG On-Screen Phone (OSP) versions prior to 4.3.010 contain an authorization bypass vulnerability. Remote attackers can send specially crafted requests to the OSP service, allowing them to bypass normal authorization mechanisms and potentially gain unauthorized access to the device or its functions.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (PoC) exploit for CVE-2014-8757, an authentication bypass vulnerability in LG's On Screen Phone (OSP) application (v4.3.009 and older) for Android smartphones. The exploit consists of two Perl scripts: 1. **osp-discovery.pl**: Listens for UDP discovery broadcast messages from the official LG OSP application and responds, making the application believe a phone running OSP is available locally. It operates on UDP port 19528. 2. **osp-proxy.pl**: Acts as a proxy, accepting incoming TCP connections from the OSP client (typically running on a PC) on port 8382. It then connects to the real LG phone's OSP service (also on port 8382) and relays traffic. The script specifically skips the authentication message, exploiting the vulnerability that allows further commands to be sent without user confirmation on the phone. The README.md provides detailed background, technical explanation, and usage instructions. The exploit enables an attacker on the same local network to gain full control over a vulnerable LG smartphone without user consent, by bypassing the OSP authentication dialog. No payload is included beyond the proxying and bypass logic, making this a PoC-level exploit. The repository is well-structured, with clear separation between discovery and exploitation components.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.