LiveActive security incident?Get immediate response
CVE Record

CVE-2007-5685: The safe_path function in shttp before 0.0.5 allows remote attackers to conduct directory traversal attacks...

The safe_path function in shttp before 0.0.5 allows remote attackers to conduct directory traversal attacks and read files via a combination of ".." and sub-directory specifiers that resolve to a pathname that is at or below the same level as the web document root, but in a different part of the directory tree.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's Takemoderate

Analyst readout for executives and security teams

Plain-English summary

CVE-2007-5685 is a directory traversal flaw in shttp before 0.0.5. A remote attacker could make the server read files outside the intended web document root in certain path layouts. The main business risk is unintended disclosure from legacy systems running this specific server.

Executive priority

Treat as a targeted legacy exposure issue, not a broad enterprise emergency. Prioritize externally reachable shttp services and systems holding sensitive local files, because successful exploitation could disclose data without authentication evidence in the bundle.

Technical view

The issue is in shttp's safe_path function before 0.0.5. Crafted paths combining parent-directory markers and subdirectory specifiers can resolve outside the intended document root while still passing the safety check. Public metadata does not provide CVSS, CWE, CPE, or detailed affected vendor data.

Likely exposure

Exposure is most likely limited to legacy internet-facing or internal hosts running shttp before 0.0.5. The CVE record’s structured affected-product fields are incomplete, so vulnerability managers should not rely on CPE matching alone.

Exploitation context

The sources describe a remotely reachable directory traversal issue, and Bugtraq disclosure indicates public technical awareness in 2007. The provided bundle does not show CISA KEV listing, active exploitation, exploit prevalence, or confirmed weaponization.

Researcher notes

The core evidence is a 2007 directory traversal disclosure and CVE description. Affected product metadata is sparse, and no CVSS or CWE is supplied. Analysis should focus on confirming real shttp deployment and version rather than assuming broad exposure.

Mitigation direction

  • Inventory systems for shttp and confirm exact version.
  • Upgrade shttp to 0.0.5 or vendor-confirmed fixed software.
  • Remove or isolate obsolete shttp instances if upgrade is unavailable.
  • Restrict network access to any remaining legacy shttp service.
  • Review vendor guidance before applying compensating controls.

Validation and detection

  • Check package, binary, or service metadata for shttp before 0.0.5.
  • Verify web roots cannot expose adjacent filesystem paths.
  • Review web server logs for suspicious traversal-like path requests.
  • Confirm scanners are not relying only on absent CPE data.
  • Document any legacy exception and compensating controls.
Prepared
Confidence
medium
Sources
6

Public sources used

Based on public source material and reviewed before publication.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2007-5685 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.