Skip to content

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

Critical severity GitHub Reviewed Published May 17, 2022 to the GitHub Advisory Database • Updated Apr 12, 2024

Package

nuget DotNetCasClient (NuGet)

Affected versions

< 1.0.2

Patched versions

1.0.2
composer jasig/phpcas (Composer)
< 1.3.3
1.3.3
maven org.jasig.cas:cas-client (Maven)
< 3.3.2
3.3.2

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.

References

Published by the National Vulnerability Database Jan 24, 2020
Published to the GitHub Advisory Database May 17, 2022
Reviewed Nov 22, 2022
Last updated Apr 12, 2024

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

2.412%
(90th percentile)

Weaknesses

CVE ID

CVE-2014-4172

GHSA ID

GHSA-9fc5-q25c-r2wr

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.