{"answers":{"affected":"4 open source packages ship an affected version, including org.apache.camel:camel-hessian. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-12633 in the wild and no public exploit code.","fix":"Upgrade org.apache.camel:camel-hessian to a fixed version for your release line: 2.19.4 or 2.20.1.","what":"CVE-2017-12633 is a critical unsafe deserialization vulnerability in Apache Camel, published on 15 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-12633 and fix it if it is affected.\n\nWhat it is: CVE-2017-12633 is a critical unsafe deserialization vulnerability in Apache Camel, published on 15 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-12633 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.camel:camel-hessian (Maven): affected from 2.0; fixed in 2.19.4\n- org.apache.camel:camel-hessian (Maven): affected from 2.0; fixed in 2.19.4\n- org.apache.camel:camel-hessian (Maven): affected from 2.20.0; fixed in 2.20.1\n- org.apache.camel:camel-hessian (Maven): affected from 2.20.0; fixed in 2.20.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-12633/ (Markdown: https://insights.sbomify.com/CVE-2017-12633/index.md)","id":"CVE-2017-12633","markdown":"https://insights.sbomify.com/CVE-2017-12633/index.md","name":"CVE-2017-12633","record":{"aliases":["GHSA-5whj-523x-6j68"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Java integration framework","requires_auth":"none","summary":"Attackers can execute arbitrary code by sending malicious serialized Java objects to the Apache Camel Hessian component.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"camel","vendor":"apache"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Apache Camel camel-hessian component vulnerable to Java object deserialization","id":"CVE-2017-12633","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"apache:camel","products":["apache:camel"],"type":"deserialization","year":"2017"},"n_packages":4,"n_references":6,"next":{"headline":"Camel-castor component in Apache Camel is vulnerable to Java object de-serialisation","id":"CVE-2017-12634"},"packages":[{"ecosystem":"Maven","fixed":["2.19.4"],"introduced":["2.0"],"last_affected":[],"package":"org.apache.camel:camel-hessian","purl":null,"source":"GHSA-5whj-523x-6j68"},{"ecosystem":"Maven","fixed":["2.19.4"],"introduced":["2.0"],"last_affected":[],"package":"org.apache.camel:camel-hessian","purl":"pkg:maven/org.apache.camel/camel-hessian","source":"GHSA-5whj-523x-6j68"},{"ecosystem":"Maven","fixed":["2.20.1"],"introduced":["2.20.0"],"last_affected":[],"package":"org.apache.camel:camel-hessian","purl":null,"source":"GHSA-5whj-523x-6j68"},{"ecosystem":"Maven","fixed":["2.20.1"],"introduced":["2.20.0"],"last_affected":[],"package":"org.apache.camel:camel-hessian","purl":"pkg:maven/org.apache.camel/camel-hessian","source":"GHSA-5whj-523x-6j68"}],"prev":{"headline":"Apache NiFi host header poisoning issue","id":"CVE-2017-12632"},"products":["Apache Camel"],"published":"2017-11-15","related":[{"cvss_score":10,"headline":"Apache camel-coap allows header injection that can lead to remote code execution","id":"CVE-2026-33453","kev_date_added":null,"published":"2026-04-27"},{"cvss_score":9.9,"headline":"Apache Camel has an incomplete fix for CVE-2025-27636","id":"CVE-2026-40453","kev_date_added":null,"published":"2026-04-27"},{"cvss_score":9.8,"headline":"Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod","id":"CVE-2026-80351","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":9.8,"headline":"Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects","id":"CVE-2026-80352","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":9.8,"headline":"Apache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection","id":"CVE-2026-71300","kev_date_added":null,"published":"2026-08-24"},{"cvss_score":9.8,"headline":"Apache Camel-Undertow: the endpoint discarded the undertow-specific header filter strategy in favour of the base HTTP one, so the undertow filtering never ran on endpoint-configured routes","id":"CVE-2026-78329","kev_date_added":null,"published":"2026-08-24"},{"cvss_score":9.8,"headline":"Apache Camel-PQC: The AWS Secrets Manager key-lifecycle manager deserializes persisted key metadata with java.io.ObjectInputStream and no ObjectInputFilter","id":"CVE-2026-43867","kev_date_added":null,"published":"2026-07-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Apache Software Foundation"]},"summary":"Attackers can execute arbitrary code by sending malicious serialized Java objects to the Apache Camel Hessian component.","url":"https://insights.sbomify.com/CVE-2017-12633/"}