PhpcasApplication · Apereo

CVE-2010-3692

MEDIUM · 6.4 CVSS v2.0 Published 2010-10-07

Fix available

A fix is available. Upgrade to after 1.1.2 or later.

See remediation →

73/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Directory traversal vulnerability in the callback function in client.php in phpCAS before 1.1.3, when proxy mode is enabled, allows remote attackers to create or overwrite arbitrary files via directory traversal sequences in a Proxy Granting Ticket IOU (PGTiou) parameter.

Technical summary

dbcve analysis · high confidence

A directory traversal vulnerability exists in phpCAS client.php before version 1.1.3 when proxy mode is enabled. The vulnerability allows remote attackers to create or overwrite arbitrary files on the server by using directory traversal sequences in the Proxy Granting Ticket IOU (PGTiou) parameter passed to the callback function.

MitigationUpdate phpCAS to version 1.1.3 or later. If proxy mode is not required in the application, disable it as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

PhpcasApplication

Affected:<= 1.1.2= 0.2= 0.3= 0.3.1= 0.3.2= 0.4= 0.4.1= 0.4.8= 0.4.9= 0.4.10= 0.4.11= 0.4.12

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Authentication: None
Confidentiality: None
Integrity: Partial
Availability: Partial

AV:N/AC:L/Au:N/C:N/I:P/A:P

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Locate phpCAS installation

Search for the client.php file or phpcas directory in your web application root, libraries, or vendor folders. Common paths include /lib/phpcas/, /vendor/phpcas/, or within authentication libraries.

Affected if phpCAS library is present in the application
Determine installed phpCAS version

Open client.php and look for a version definition near the top of the file, typically in comments or a version constant. Compare this to the affected versions: <= 1.1.2, or 0.2, 0.3, 0.3.1, 0.3.2, 0.4, 0.4.1, 0.4.8, 0.4.9, 0.4.10, 0.4.11, 0.4.12

Affected if The version is 1.1.2 or lower, or matches any of the specific vulnerable versions listed
Check if proxy mode is enabled

Search your application code for calls to phpCAS proxy methods such as phpCAS::proxy(), CAS::proxy(), or configuration flags like CAS_PROXYIX. Also inspect any phpCAS configuration files for proxy-related settings.

Affected if Proxy mode is enabled in the phpCAS configuration or usage
Identify callback endpoint exposure

Locate the callback URL handler that processes the PGTiou parameter. This is typically set via phpCAS::setCallbackURL() or handles the proxy granting ticket callback. Verify if this endpoint is publicly accessible.

Affected if A proxy callback URL is configured and accessible to unauthenticated users

The environment is affected if phpCAS version 1.1.2 or lower (or one of the specific vulnerable 0.x versions) is installed AND proxy mode is enabled, allowing the PGTiou parameter to be manipulated via the callback endpoint.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Upgrade available Upgrade to a release after 1.1.2

Interim mitigation

Update phpCAS to version 1.1.3 or later. If proxy mode is not required in the application, disable it as a defense-in-depth measure.

Fix this in Phpcas Scoped from the published advisory

Consultation2.0 h
Implementation1.0 h
Testing3.0 h
Review / QA1.0 h

7.0 hours of engineering $1,210

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2010-3692 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-3692 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2010-3692?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsUpgrade to after 1.1.2 or later

Severity 6.4 Medium

Exploit likelihood EPSS, next 30 days 3.6%

Affects: Phpcas

Remediation

Need this fixed?

Fix this in Phpcas 7 hrs · Low

Typical engagement from $1,210

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2010-3692 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References