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

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.

A vulnerability was found in Apache Camel up to 2.19.3/2.20.0 and classified as critical. Affected by this issue is an unknown functionality of the component camel-hessian. The manipulation as part of a Java Object leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is confidentiality, integrity, and availability. CVE summarizes:

The camel-hessian 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 presented 11/15/2017 (Website). The advisory is available at camel.apache.org. This vulnerability is handled as CVE-2017-12633 since 08/07/2017. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not 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.

See 109419 for similar entry.






CPE 2.3info

CPE 2.2info


VulDB CVSS-B Score: 🔍
VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍


VulDB Meta Base Score: 8.5
VulDB 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: 🔍



VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍


Class: Deserialization
CWE: CWE-502 / CWE-20
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍


Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍


Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Camel 2.19.4/2.20.1


08/07/2017 🔍
08/07/2017 +0 days 🔍
11/15/2017 +100 days 🔍
11/15/2017 +0 days 🔍
11/15/2017 +0 days 🔍
11/16/2017 +1 days 🔍
01/10/2023 +1881 days 🔍


Vendor: apache.org

Advisory: RHSA-2018:0319
Researcher: Moritz Bechler
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-12633 (🔍)
SecurityFocus: 101874 - Apache Camel CVE-2017-12633 Deserialization Remote Code Execution Vulnerability

See also: 🔍


Created: 11/16/2017 10:23 AM
Updated: 01/10/2023 11:51 AM
Changes: 11/16/2017 10:23 AM (62), 12/06/2019 03:58 PM (4), 01/23/2021 06:01 PM (2), 01/10/2023 11:51 AM (3)
Complete: 🔍


No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!