Menu

Star on GitHub · 3.2k

CVE-2010-3691

3.3 · LOW

PGTStorage/pgt-file.php in phpCAS before 1.1.3, when proxy mode is enabled, allows local users to overwrite arbitrary files via a symlink attack on an unspecified file.

Published Oct 7, 2010apereoCWE-59EPSS 0.35%

Overview

CVE-2010-3691 is a low-severity vulnerability affecting apereo phpcas. It was published on October 7, 2010 and has a CVSS 2.0 base score of 3.3 (LOW).

This vulnerability has a CVSS 2.0 base score of 3.3, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

PGTStorage/pgt-file.php in phpCAS before 1.1.3, when proxy mode is enabled, allows local users to overwrite arbitrary files via a symlink attack on an unspecified file.

Remediation

Check the references section for vendor advisories and patches from apereo. Update phpcas 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
apereophpcas0Affected

Frequently asked questions

What is CVE-2010-3691?

CVE-2010-3691 is a low-severity vulnerability affecting apereo phpcas. It was published on October 7, 2010 and has a CVSS 2.0 base score of 3.3 (LOW).

How severe is CVE-2010-3691?

This vulnerability has a CVSS 2.0 base score of 3.3, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2010-3691?

Check the references section for vendor advisories and patches from apereo. Update phpcas 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-2010-3691?

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

View all