How severe is CVE-2014-4172?

CVE-2014-4172 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2014-4172?

CVE-2014-4172 affects the following packages: org.jasig.cas:cas-client (Maven), DotNetCasClient (NuGet), jasig/phpcas (Packagist). Ecosystems affected: Maven, NuGet, Packagist.

How do I fix CVE-2014-4172?

Update org.jasig.cas:cas-client to 3.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-4172 is resolved across your whole dependency graph.

How do I detect CVE-2014-4172 in my Maven, NuGet, Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jasig.cas:cas-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2014-4172 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2014-4172 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-4172 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2014-4172?

CVE-2014-4172 has an EPSS (Exploit Prediction Scoring System) score of 6.1%, placing it in the 93th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-4172?

CVE-2014-4172 is classified as CWE-74 (CWE-74). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-4172 published, and has it been updated?

CVE-2014-4172 was published on January 24, 2020 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven.NET NuGet🐘 Packagist

Not in CISA KEV

CRITICAL severity

CVE-2014-4172 — cas-client

CRITICALFix: Jasig/dotnet-cas-client@f0e0300

CVE-2014-4172 is a critical-severity (CVSS 9.8) CWE-74 vulnerability in org.jasig.cas:cas-client. A fix is available for org.jasig.cas:cas-client — see the affected versions and patch details below.

Jasig Java CAS Client, .NET CAS Client, and phpCAS contain URL parameter injection vulnerability

Also known asGHSA-9fc5-q25c-r2wr

Published

Jan 24, 2020

Updated

Apr 16, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

6.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

☕org.jasig.cas:cas-client.NETDotNetCasClient🐘jasig/phpcas

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven, NuGet, Packagist packages — download data is not available via public APIs for these ecosystems.

Description

A URL parameter injection vulnerability was found in the back-channel ticket validation step of the CAS protocol in Jasig Java CAS Client before 3.3.2, .NET CAS Client before 1.0.2, and phpCAS before 1.3.3 that allow remote attackers to inject arbitrary web script or HTML via the (1) service parameter to validation/AbstractUrlBasedTicketValidator.java or (2) pgtUrl parameter to validation/Cas20ServiceTicketValidator.java.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jasig.cas:cas-client`	all versions	3.3.2`org.jasig.cas:cas-client:3.3.2`
.NETNuGet	`DotNetCasClient`	all versions	1.0.2`dotnet add package DotNetCasClient --version 1.0.2`
🐘Packagist	`jasig/phpcas`	all versions	1.3.3`composer require jasig/phpcas:^1.3.3`

Affected Products

5 products · 5 configurations

Application

.net cas clientapereo

< 1.0.2

range

Application

java cas clientapereo

< 3.3.2

range

Application

phpcasapereo

< 1.3.3

range

debian linuxdebian

1 version

7.0

fedorafedoraproject

1 version

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jasig.cas:cas-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jasig.cas:cas-client to 3.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-4172 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat JBoss Portal 6.2	`cas-client`	RHSA-2015:1009

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-4172 in your dependencies?

Find it across Maven, NuGet, Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2014-4172 — cas-client

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2014-4172 in your dependencies?