Loading vulnerability…
Gibbon v25.0.0 contains a Local File Inclusion (LFI) vulnerability that allows an attacker to include and read the contents of files located within the installation directory via crafted input. This can expose sensitive files and application data present on the server.
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 (1 hidden).
This repository contains a Python exploit script (CVE-2023-34598.py) and a README.md. The script targets a Local File Inclusion (LFI) vulnerability (CVE-2023-34598) in Gibbon v25.0.0. It provides two main functions: (1) scanning a target URL to determine if it is vulnerable by requesting '/?q=gibbon.sql' and analyzing the response for SQL dump markers, and (2) displaying a FOFA query to help find more targets. If a target is found vulnerable, the script creates a local directory (e.g., 'Gibbon_dump'), saves the target URL in '!target.txt', and writes the extracted SQL dump to 'gibbon.sql'. The README provides detailed usage instructions, requirements, and legal disclaimers. The exploit is operational, providing a working method to extract sensitive database information from vulnerable Gibbon installations.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.