Loading vulnerability…
CVE-2024-31848 is a path traversal vulnerability in the Java version of CData API Server (and related CData Java products) when deployed using the embedded Jetty server (up to Jetty 10.0.20, 11.0.20, and 12.0.7). The vulnerability allows unauthenticated remote attackers to craft special requests to backend endpoints, such as getSettings.rsb, and bypass authentication, leading to unauthorized file read and potentially complete administrative access to the application. The vulnerability is not present in .NET installations or deployments using servlet containers other than Jetty.
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 contains a Python proof-of-concept exploit for CVE-2024-31848, CVE-2024-31849, CVE-2024-31850, and CVE-2024-31851, which are path traversal vulnerabilities affecting CData applications running on embedded Jetty servers. The main file, CVE-2024-31848.py, is a command-line tool that takes a target URL and attempts to exploit the vulnerability by sending a crafted HTTP GET request to retrieve the getSettings.rsb file via a path traversal vector (ui/..\src\getSettings.rsb?@json). If successful, the script prints the contents of the file, which may contain sensitive configuration information. The README.md provides usage instructions and context about the vulnerability. The exploit is operational as a PoC and demonstrates the ability to read arbitrary files from vulnerable servers. No hardcoded IPs or domains are present; the user supplies the target URL.
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.