Jasig CAS Server up to 3.4.12.0/3.5.2.0 Google Account SamlUtils.java XML Data xml external entity reference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Jasig CAS Server up to 3.4.12.0/3.5.2.0 and classified as critical. Affected by this issue is some unknown functionality of the file java/org/jasig/cas/util/SamlUtils.java of the component Google Account Handler. Performing a manipulation as part of XML Data results in xml external entity reference. This vulnerability was named CVE-2014-2296. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.
Details
A vulnerability classified as critical has been found in Jasig CAS Server up to 3.4.12.0/3.5.2.0. This affects an unknown part of the file java/org/jasig/cas/util/SamlUtils.java of the component Google Account Handler. The manipulation as part of a XML Data leads to a xml external entity reference vulnerability. CWE is classifying the issue as CWE-611. The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
XML external entity (XXE) vulnerability in java/org/jasig/cas/util/SamlUtils.java in Jasig CAS server before 3.4.12.1 and 3.5.x before 3.5.2.1, when Google Accounts Integration is enabled, allows remote unauthenticated users to bypass authentication via crafted XML data.
The bug was discovered 04/02/2014. The weakness was presented 07/20/2018 (Website). The advisory is shared at jasig.275507.n4.nabble.com. This vulnerability is uniquely identified as CVE-2014-2296 since 03/06/2014. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 1570 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 3.4.12.1 or 3.5.2.1 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Xml external entity referenceCWE: CWE-611 / CWE-610
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: CAS Server 3.4.12.1/3.5.2.1
Timeline
03/06/2014 🔍04/02/2014 🔍
07/20/2018 🔍
07/20/2018 🔍
07/21/2018 🔍
03/08/2020 🔍
Sources
Advisory: jasig.275507.n4.nabble.comStatus: Not defined
CVE: CVE-2014-2296 (🔍)
GCVE (CVE): GCVE-0-2014-2296
GCVE (VulDB): GCVE-100-122013
Entry
Created: 07/21/2018 09:40Updated: 03/08/2020 23:14
Changes: 07/21/2018 09:40 (61), 03/08/2020 23:14 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.