Menu

Star on GitHub · 3.2k

CVE-2009-1354

4.0 · MEDIUM

Directory traversal vulnerability in Mongoose 2.4 allows remote attackers to read arbitrary files via a ..

Published Apr 21, 2009sergey_lyubkaCWE-22EPSS 2.27%

Overview

CVE-2009-1354 is a medium-severity vulnerability affecting sergey_lyubka mongoose. It was published on April 21, 2009 and has a CVSS 2.0 base score of 4.0 (MEDIUM).

This vulnerability has a CVSS 2.0 base score of 4.0, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

Directory traversal vulnerability in Mongoose 2.4 allows remote attackers to read arbitrary files via a .. (dot dot) in the URI.

Remediation

Check the references section for vendor advisories and patches from sergey_lyubka. Update mongoose to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2009-1354?

CVE-2009-1354 is a medium-severity vulnerability affecting sergey_lyubka mongoose. It was published on April 21, 2009 and has a CVSS 2.0 base score of 4.0 (MEDIUM).

How severe is CVE-2009-1354?

This vulnerability has a CVSS 2.0 base score of 4.0, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2009-1354?

Check the references section for vendor advisories and patches from sergey_lyubka. Update mongoose to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2009-1354?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2009-1354 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2009

View all