Menu

Star on GitHub · 3.2k

CVE-2009-0240

3.5 · LOW

listing.php in WebSVN 2.0 and possibly 1.7 beta, when using an SVN authz file, allows remote authenticated users to read changelogs or diffs for restricted projects via a modified repname parameter.

Published Jan 21, 2009tigrisCWE-264EPSS 1.60%

Overview

CVE-2009-0240 is a low-severity vulnerability affecting tigris websvn. It was published on January 21, 2009 and has a CVSS 2.0 base score of 3.5 (LOW).

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

Technical description

listing.php in WebSVN 2.0 and possibly 1.7 beta, when using an SVN authz file, allows remote authenticated users to read changelogs or diffs for restricted projects via a modified repname parameter.

Remediation

Check the references section for vendor advisories and patches from tigris. Update websvn 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-0240?

CVE-2009-0240 is a low-severity vulnerability affecting tigris websvn. It was published on January 21, 2009 and has a CVSS 2.0 base score of 3.5 (LOW).

How severe is CVE-2009-0240?

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

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

Check the references section for vendor advisories and patches from tigris. Update websvn 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-0240?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2009-0240 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 LOW CVEs from 2009

View all