Loading vulnerability…
A format string vulnerability exists in the gpsd_report function of BerliOS GPD daemon (gpsd, formerly pygps) versions 1.9.0 through 2.7. The vulnerability is due to improper handling of user-supplied input in syslog calls, where format string specifiers in certain GPS requests are not sanitized. This allows remote attackers to inject format string specifiers, potentially leading to arbitrary code execution.
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 (3 hidden).
This repository contains a single Metasploit module (modules/exploits/linux/http/gpsd_format_string.rb) that exploits a format string vulnerability (CVE-2004-1388) in the Berlios GPSD server. The exploit targets multiple versions of GPSD (1.91 through 2.7) and specific Linux distributions (SuSE, Slackware) by sending a specially crafted payload over TCP port 2947, the default GPSD service port. The module allows the attacker to execute arbitrary code on the target system with the privileges of the GPSD process. The payload is customizable and supports standard Metasploit post-exploitation actions. The code is written in Ruby and follows the standard Metasploit module structure, making it easy to use within the framework. No hardcoded IP addresses or URLs are present; the only fingerprintable endpoint is the TCP port 2947 used by GPSD.
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.