CVE-2014-4172 is an improper URL-encoding vulnerability in the CAS protocol back-channel ticket-validation process in Jasig Java CAS Client before 3.3.2, .NET CAS Client before 1.0.2, and phpCAS before 1.3.3. The affected validation logic fails to safely encode attacker-controlled service and proxy-granting-ticket callback parameters when constructing validation requests. A remote attacker can inject URL parameters, including arbitrary HTML or web script in affected flows, and can cause a ticket issued for one CAS service to be validated against another service, bypassing the CAS service-binding security constraint.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
CAS client security-constraint bypass through URL parameter injection.
An improper URL-encoding flaw in back-channel ticket validation in the JA-SIG CAS client. A remote attacker could inject URL parameters to bypass security constraints.
An important URL-parameter injection flaw in CAS back-channel ticket validation. Remote unauthenticated attackers can inject arbitrary HTML or web script through the service or pgtUrl parameters, potentially bypassing security constraints.
An improper URL-encoding / URL-parameter-injection vulnerability in CAS back-channel ticket validation. It can allow a valid ticket issued for one service to be used against another service, enabling illicit authentication proxying, unauthorized data disclosure, or privilege escalation.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.