org.apache.camel:camel-core vulnerabilities
The Core Camel Framework
- Registry
- Maven
- Latest
- 4.23.0
- License
- Apache-2.0
11 known advisories
The latest version, 4.23.0, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.apache.camel:camel-core -DdepVersion=4.23.0 -DforceVersion=trueIs your project on an affected org.apache.camel:camel-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.apache.camel:camel-core
Apache Camel data exposure vulnerability
- Affected
- >=3.0.0 <3.21.4 · >=3.22.0 <3.22.1 · >=4.0.0 <4.0.4 · >=4.1.0 <4.4.0
- Fixed in
- 3.21.4, 3.22.1, 4.0.4, 4.4.0
Improper Control of Generation of Code in Apache Camel
- Affected
- <2.9.7 · >=2.10.0 <2.10.7 · >=2.11.0 <2.11.2 · >=2.12.0 <2.12.1
- Fixed in
- 2.9.7, 2.10.7, 2.11.2, 2.12.1
Improper Input Validation in Apache Camel
- Affected
- <3.2.0
- Fixed in
- 3.2.0
XML External Entity injection in Apache Camel
- Affected
- <2.24.0
- Fixed in
- 2.24.0
Path Traversal in Apache Camel
- Affected
- >=2.21.0 <2.21.5 · >=2.22.0 <2.22.3 · >=2.23.0 <2.23.1
- Fixed in
- 2.21.5, 2.22.3, 2.23.1
Apache Camel's XSLT component allows remote attackers to execute arbitrary Java methods
- Affected
- >=2.11.0 <2.11.4 · >=2.12.0 <2.12.3
- Fixed in
- 2.11.4, 2.12.3
Apache Camel's XSLT component allows remote attackers to read arbitrary files
- Affected
- <2.11.4 · >=2.12.0 <2.12.3
- Fixed in
- 2.11.4, 2.12.3
Apache Camel's Validation Component is vulnerable against SSRF via remote DTDs and XXE.
- Affected
- <2.17.6 · >=2.18.0 <2.18.2
- Fixed in
- 2.17.6, 2.18.2
Apache Camel allows remote actor to read arbitrary files via external entity in invalid XML string or GenericFile object
- Affected
- <2.13.4 · >=2.14.0 <2.14.2
- Fixed in
- 2.13.4, 2.14.2
Apache Camel XML External Entity vulnerability
- Affected
- <2.13.4 · >=2.14.0 <2.14.2
- Fixed in
- 2.13.4, 2.14.2
Apache is vulnerable to XXE in XSD validation processor
- Affected
- >=2.20.0 <2.20.4 · >=2.21.0 <2.21.1
- Fixed in
- 2.20.4, 2.21.1
Is your org.apache.camel:camel-core version vulnerable?
- org.apache.camel:camel-core 4.23No known advisories in 4.23.0
- org.apache.camel:camel-core 4.22No known advisories in 4.22.2
- org.apache.camel:camel-core 4.21No known advisories in 4.21.0
- org.apache.camel:camel-core 4.20No known advisories in 4.20.0
- org.apache.camel:camel-core 4.19No known advisories in 4.19.0
- org.apache.camel:camel-core 4.18No known advisories in 4.18.5
- org.apache.camel:camel-core 3.22No known advisories in 3.22.4
- org.apache.camel:camel-core 3.21No known advisories in 3.21.5
- org.apache.camel:camel-core 3.201 advisory in 3.20.9
- org.apache.camel:camel-core 3.191 advisory in 3.19.0
- org.apache.camel:camel-core 3.181 advisory in 3.18.8
- org.apache.camel:camel-core 3.171 advisory in 3.17.0
- org.apache.camel:camel-core 2.251 advisory in 2.25.4
- org.apache.camel:camel-core 2.241 advisory in 2.24.3
- org.apache.camel:camel-core 2.232 advisories in 2.23.4
- org.apache.camel:camel-core 2.222 advisories in 2.22.5
- org.apache.camel:camel-core 2.212 advisories in 2.21.5
- org.apache.camel:camel-core 2.202 advisories in 2.20.4
Which of your client projects still run an old org.apache.camel:camel-core?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.