CVE-2023-34442 is a low-severity (CVSS 3.3) Information Exposure vulnerability in org.apache.camel:camel-jira. A fix is available for org.apache.camel:camel-jira — see the affected versions and patch details below.
Apache Camel JIRA: Temporary file information disclosure in Camel-Jira
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-34442.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.camel:camel-jira☕org.apache.camel:camel-jira☕org.apache.camel:camel-jira☕org.apache.camel:camel-jiraReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Software Foundation Apache Camel. This issue affects Apache Camel from 3.X through <=3.14.8, from 3.18.X through <=3.18.7, from 3.20.X through <= 3.20.5, from 4.X through <= 4.0.0-M3.
Users should upgrade to 3.14.9, 3.18.8, 3.20.6 or 3.21.0 and for users on Camel 4.x update to 4.0.0-RC1
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.camel:camel-jira | ≥ 3.0.0-M3&&< 3.14.9 | 3.14.9org.apache.camel:camel-jira:3.14.9 |
| ☕Maven | org.apache.camel:camel-jira | ≥ 3.15.0&&< 3.18.8 | 3.18.8org.apache.camel:camel-jira:3.18.8 |
| ☕Maven | org.apache.camel:camel-jira | ≥ 3.20.0&&< 3.20.6 | 3.20.6org.apache.camel:camel-jira:3.20.6 |
| ☕Maven | org.apache.camel:camel-jira | ≥ 4.0.0-M1&&< 4.0.0-RC1 | 4.0.0-RC1org.apache.camel:camel-jira:4.0.0-RC1 |
Affected Products
camelapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.camel:camel-jira, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.camel:camel-jira to 3.14.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-34442 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2023-34442 in your dependencies?
Find it across Maven, including transitive dependencies.