Apache Camel up to 2.19.3/2.20.0 camel-castor Java Object deserialization

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Apache Camel up to 2.19.3/2.20.0. This affects an unknown part of the component camel-castor. Performing a manipulation as part of Java Object results in deserialization. This vulnerability is cataloged as CVE-2017-12634. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability was found in Apache Camel up to 2.19.3/2.20.0. It has been classified as critical. This affects some unknown functionality of the component camel-castor. The manipulation as part of a Java Object leads to a deserialization vulnerability. CWE is classifying the issue as CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The camel-castor component in Apache Camel 2.x before 2.19.4 and 2.20.x before 2.20.1 is vulnerable to Java object de-serialisation vulnerability. De-serializing untrusted data can lead to security flaws.
The bug was discovered 08/07/2017. The weakness was shared 11/15/2017 by Man Yue Mo (Website). It is possible to read the advisory at camel.apache.org. This vulnerability is uniquely identified as CVE-2017-12634 since 08/07/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 100 days. During that time the estimated underground price was around $5k-$25k.
Upgrading to version 2.19.4 or 2.20.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 101876†). The entry VDB-109418 is related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
- 2.0
- 2.1
- 2.2
- 2.3
- 2.4
- 2.5
- 2.6
- 2.7
- 2.8
- 2.9
- 2.10
- 2.11
- 2.12
- 2.13
- 2.14
- 2.15
- 2.16
- 2.17
- 2.18
- 2.19
- 2.19.0
- 2.19.1
- 2.19.2
- 2.19.3
- 2.20.0
License
Website
- Vendor: https://www.apache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.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: DeserializationCWE: CWE-502 / CWE-20
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: Camel 2.19.4/2.20.1
Timeline
08/07/2017 🔍08/07/2017 🔍
11/15/2017 🔍
11/15/2017 🔍
11/15/2017 🔍
11/16/2017 🔍
01/10/2023 🔍
Sources
Vendor: apache.orgAdvisory: RHSA-2018:0319
Researcher: Man Yue Mo
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-12634 (🔍)
GCVE (CVE): GCVE-0-2017-12634
GCVE (VulDB): GCVE-100-109419
SecurityFocus: 101876 - Apache Camel CVE-2017-12634 Deserialization Remote Code Execution Vulnerability
See also: 🔍
Entry
Created: 11/16/2017 10:25Updated: 01/10/2023 11:58
Changes: 11/16/2017 10:25 (62), 12/06/2019 16:02 (5), 01/10/2023 11:58 (4)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.