CVE-2013-6056
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOSSIM before 4.3.3.1 has tele_compress.php path traversal vulnerability
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA path traversal vulnerability exists in tele_compress.php in OSSIM (Open Source Security Information Management) versions before 4.3.3.1. The vulnerability allows remote attackers to access files outside the web root directory by manipulating file path parameters, potentially exposing sensitive system files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.3.3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm OSSIM installationIdentify if Alienvault OSSIM is installed on the system by checking for OSSIM-specific directories, services, or packages (e.g., look for /etc/ossim, /var/ossim, or the 'ossim-server' service)Affected if OSSIM is installed and the version is below 4.3.3.1
-
Determine OSSIM versionLocate the installed OSSIM version by inspecting version files, package managers, or the OSSIM web interface login banner. Compare the found version against the affected range of versions before 4.3.3.1Affected if The installed version is any version prior to 4.3.3.1
-
Locate tele_compress.phpSearch for the tele_compress.php file within the OSSIM web directory structure, typically found under the web root (commonly /var/www or /var/www/html in OSSIM deployments)Affected if The tele_compress.php file exists in the web-accessible directory
-
Verify web access to vulnerable scriptCheck if the web server configuration allows access to tele_compress.php by testing with a direct HTTP request to the script URL (e.g., https://your-ossim-host/tele_compress.php)Affected if The script responds to HTTP requests and is not blocked by the web server
-
Test path traversal parameterIf tele_compress.php is accessible, examine if it accepts file path parameters by reviewing the script source code or by sending a test request with directory traversal patterns (e.g., ../../etc/passwd) to see if the script returns file contents outside the web rootAffected if The script accepts path parameters and returns content from files outside the intended directory
You are affected if OSSIM is installed with a version before 4.3.3.1 and the tele_compress.php script is accessible via the web server, allowing path traversal attacks to read arbitrary files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data4.3.3.1
Upgrade OSSIM to version 4.3.3.1 or later to obtain the patched tele_compress.php. As a temporary measure, restrict direct access to tele_compress.php via web server configuration or deploy a WAF rule to block directory traversal patterns in requests to this endpoint.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6056 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-6056 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data