LiveActive security incident?Get immediate response
CVE Record

CVE-2011-4350: Yaws 1.91 has a directory traversal vulnerability in the way certain URLs are processed.

Yaws 1.91 has a directory traversal vulnerability in the way certain URLs are processed. A remote authenticated user could use this flaw to obtain content of arbitrary local files via specially-crafted URL request.

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

Security readout for executives and security teams

Plain-English summary

Yaws 1.91 has a directory traversal flaw that can let an authenticated remote user read local files the server can access. The public bundle does not show active exploitation or a CVSS score. Business urgency depends on whether Yaws 1.91 is deployed and whether exposed accounts can reach it.

Executive priority

Treat as a targeted exposure review rather than an emergency unless Yaws 1.91 is confirmed in use. Prioritize systems exposed to customers, partners, or broad internal user groups because the impact is local file disclosure.

Technical view

The issue is URL-processing directory traversal in Yaws 1.91. An authenticated remote user may obtain arbitrary local file contents through crafted URL requests. The source bundle names only Yaws 1.91 as affected and does not provide CVSS, CWE, exploit status, or definitive fixed-version details.

Likely exposure

Exposure is likely limited to organizations running Yaws 1.91, especially reachable web services with authenticated user access. Evidence in the bundle does not identify other products, versions, or unauthenticated exposure.

Exploitation context

No CISA KEV listing is indicated, and the provided sources do not state active exploitation. The described impact is sensitive file disclosure after authentication, which can support follow-on compromise if secrets, configuration files, or credentials are exposed.

Researcher notes

The bundle is sparse: no CVSS, CWE, exploit evidence, or confirmed fixed version is included. Avoid broad version claims. Focus validation on Yaws 1.91 deployments, authentication boundary, service-account file access, and distro-specific advisory status.

Mitigation direction

  • Inventory internet-facing and internal services for Yaws 1.91 installations.
  • Check Yaws, Debian, and Red Hat guidance for fixed packages or supported upgrade paths.
  • Restrict access to affected authenticated interfaces until remediation is confirmed.
  • Review application permissions to limit readable local files exposed through the web server.
  • Monitor authenticated web activity for abnormal file-path access attempts.

Validation and detection

  • Confirm whether any deployed package reports Yaws version 1.91.
  • Map affected services to authentication requirements and exposed user populations.
  • Review vendor or distro advisories for the exact remediation status.
  • Assess whether sensitive local files are readable by the Yaws service account.
  • Check relevant logs for unusual authenticated file-access request patterns.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

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-2011-4350 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
6Source 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
yawsyaws1.91Listed
Weakness

CWE details

No CWE listed

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