HighPublic exploit

Path Traversal in XBMC 11 Embedded HTTP Server

IdentifiersCVE-2012-10024CWE-22· Improper Limitation of a Pathname…

XBMC version 11, including builds up to the 2012-11-04 nightly release, contains a path traversal vulnerability in its embedded HTTP server. When the HTTP interface is accessed using HTTP Basic Authentication, the server does not properly sanitize URI path input before resolving requested resources. This allows an authenticated attacker to traverse outside the intended web document root and access arbitrary files on the underlying host filesystem. The issue is an arbitrary file-read vulnerability affecting the embedded web server component rather than a code execution flaw.

For your environment

Are you exposed to this one?

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.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an authenticated attacker to read arbitrary files accessible to the XBMC process outside the intended HTTP-served directory. Depending on host configuration, this can expose sensitive local data such as application configuration files, stored credentials, system files, and other private content. The primary security impact is confidentiality loss; the provided information does not indicate file modification, deletion, or code execution.

Mitigation

If you can’t patch tonight, do this now.

Disable the embedded HTTP server if it is not required. If it must remain enabled, restrict access to trusted management networks only, avoid exposing it to untrusted users or the public Internet, and enforce strong unique credentials for HTTP Basic Authentication. Additional compensating controls include host-based firewalling, reverse-proxy access restrictions, and minimizing sensitive files readable by the XBMC service account.

Remediation

Patch, then assume compromise.

Upgrade XBMC to a version in which the embedded HTTP server properly sanitizes and constrains requested URI paths to the intended document root. If a fixed version is not immediately available, disable or remove exposure of the embedded HTTP server until an update can be applied. Review and rotate any credentials or secrets that may have been stored in files readable by the XBMC process and potentially exposed through this issue.

PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app

xbmc_traversal.rbMaturityWeaponizedFrameworkmetasploitVerified exploit

This repository contains a single Metasploit auxiliary module (modules/auxiliary/gather/xbmc_traversal.rb) that exploits a directory traversal vulnerability in XBMC 11 (up to the 2012-11-04 nightly build). The module allows an attacker to download arbitrary files from the XBMC web server by sending a crafted HTTP GET request with directory traversal sequences. The exploit requires valid HTTP credentials (default: xbmc/xbmc) and targets the web server running on port 8080 by default. The module is operational, providing file download capability but not remote code execution. The code is written in Ruby and is structured as a standard Metasploit module, with configurable options for the target file path, traversal depth, and HTTP credentials. The main attack vector is network-based, leveraging HTTP requests to exploit the vulnerability.

Disclosed Nov 4, 2012rubynetwork

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

UberriderMediacenterapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

4 SOURCESView more in app

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4