What is CVE-2014-4172?

CVE-2014-4172 is a critical-severity security vulnerability in DotNetCasClient (nuget), affecting versions < 1.0.2. It is fixed in 1.0.2, 3.3.2, 1.3.3.

How severe is CVE-2014-4172?

CVE-2014-4172 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2014-4172?

DotNetCasClient (nuget) versions < 1.0.2; org.jasig.cas:cas-client (maven) versions < 3.3.2; jasig/phpcas (composer) versions < 1.3.3.

Is there a fix for CVE-2014-4172?

Yes. CVE-2014-4172 is fixed in 1.0.2, 3.3.2, 1.3.3. Upgrade to this version or later.

Is CVE-2014-4172 exploitable, and should I be worried?

Whether CVE-2014-4172 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2014-4172 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2014-4172 in DotNetCasClient

Q: How severe is CVE-2014-4172?

CVE-2014-4172 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2014-4172?

DotNetCasClient (nuget) versions < 1.0.2; org.jasig.cas:cas-client (maven) versions < 3.3.2; jasig/phpcas (composer) versions < 1.3.3.

Q: Is there a fix for CVE-2014-4172?

Yes. CVE-2014-4172 is fixed in 1.0.2, 3.3.2, 1.3.3. Upgrade to this version or later.

Q: Is CVE-2014-4172 exploitable, and should I be worried?

Whether CVE-2014-4172 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2014-4172 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2014-4172?

Upgrade: DotNetCasClient to 1.0.2 or later, org.jasig.cas:cas-client to 3.3.2 or later, jasig/phpcas to 1.3.3 or later.

Summary

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

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.

Impact

CVE-2014-4172 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.0.2, 3.3.2, 1.3.3); upgrading removes the vulnerable code path.

Affected versions

DotNetCasClient (< 1.0.2) org.jasig.cas:cas-client (< 3.3.2) jasig/phpcas (< 1.3.3)

Security releases

DotNetCasClient → 1.0.2 (nuget) org.jasig.cas:cas-client → 3.3.2 (maven) jasig/phpcas → 1.3.3 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

DotNetCasClient to 1.0.2 or later; org.jasig.cas:cas-client to 3.3.2 or later; jasig/phpcas to 1.3.3 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2014-4172? CVE-2014-4172 is a critical-severity security vulnerability in DotNetCasClient (nuget), affecting versions < 1.0.2. It is fixed in 1.0.2, 3.3.2, 1.3.3.
How severe is CVE-2014-4172? CVE-2014-4172 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2014-4172?
- DotNetCasClient (nuget) (versions < 1.0.2)
- org.jasig.cas:cas-client (maven) (versions < 3.3.2)
- jasig/phpcas (composer) (versions < 1.3.3)
Is there a fix for CVE-2014-4172? Yes. CVE-2014-4172 is fixed in 1.0.2, 3.3.2, 1.3.3. Upgrade to this version or later.
Is CVE-2014-4172 exploitable, and should I be worried? Whether CVE-2014-4172 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2014-4172 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2014-4172?
- Upgrade DotNetCasClient to 1.0.2 or later
- Upgrade org.jasig.cas:cas-client to 3.3.2 or later
- Upgrade jasig/phpcas to 1.3.3 or later