dbcve.org
CamelApplication · Apache

CVE-2025-30177

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-01
Fix available
A fix is available. Upgrade to 4.8.6 / 4.10.3 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Bypass/Injection vulnerability in Apache Camel in Camel-Undertow component under particular conditions. This issue affects Apache Camel: from 4.10.0 before 4.10.3, from 4.8.0 before 4.8.6. Users are recommended to upgrade to version 4.10.3 for 4.10.x LTS and 4.8.6 for 4.8.x LTS. Camel undertow component is vulnerable to Camel message header injection, in particular the custom header filter strategy used by the component only filter the "out" direction, while it doesn't filter the "in" direction. This allows an attacker to include Camel specific headers that for some Camel components can alter the behaviour such as the camel-bean component, or the camel-exec component.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Apache Camel Undertow component has a header injection vulnerability due to its custom header filter strategy only filtering headers in the 'out' direction while leaving the 'in' direction unfiltered. This allows attackers to inject Camel-specific headers that can manipulate the behavior of downstream components like camel-bean or camel-exec.

MitigationUpgrade Apache Camel to version 4.10.3 or 4.8.6 (depending on your branch) to obtain the patched header filter strategy that properly filters incoming direction headers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CamelApplication
Affected:>= 4.8.0, < 4.8.6>= 4.10.0, < 4.10.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Camel version in use
    Inspect project dependencies (Maven pom.xml, Gradle build.gradle) or check the camel-core JAR manifest. Run: grep -r 'camel' pom.xml | grep version or examine META-INF/MANIFEST.MF inside camel-core jar
    Affected if Version is 4.8.0 through 4.8.5, or 4.10.0 through 4.10.2
  2. Confirm Undertow component is deployed
    Search for camel-undertow dependency in your build configuration (pom.xml, build.gradle) or verify the camel-undertow jar is present in the classpath. Run: find . -name 'camel-undertow*.jar'
    Affected if camel-undertow dependency or JAR is present in the runtime
  3. Locate HeaderFilterStrategy configuration
    Search Java code and XML route definitions for implementations of org.apache.camel.spi.HeaderFilterStrategy, or look for <headerFilterStrategy> elements in XML route files. Search: grep -r 'HeaderFilterStrategy' .
    Affected if A custom or extended HeaderFilterStrategy is configured for the Undertow endpoint
  4. Verify if incoming header filtering is disabled
    Inspect the HeaderFilterStrategy implementation or configuration for the doVisitHeader method, or check if setCamelHeaderFilter is configured to filter only outbound headers. Examine the route builder code for undertow: configuration
    Affected if The HeaderFilterStrategy explicitly filters only 'out' direction headers or has logic that skips 'in' direction header validation

You are affected if Apache Camel versions 4.8.0-4.8.5 or 4.10.0-4.10.2 are running with the camel-undertow component and a custom header filter strategy that does not filter incoming direction headers is in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.8.6 / 4.10.3 or later
Fixed in 4.8.64.10.3
Interim mitigation

Upgrade Apache Camel to version 4.10.3 or 4.8.6 (depending on your branch) to obtain the patched header filter strategy that properly filters incoming direction headers.

Recommended fix High confidence

4.10.3 for 4.10.x LTS; 4.8.6 for 4.8.x LTS

  1. 1. Identify the current Apache Camel version in use by checking your project's dependency management file (e.g., pom.xml for Maven or build.gradle for Gradle)
  2. 2. Locate all Camel dependencies, particularly the camel-undertow component, and note their current versions
  3. 3. For Camel 4.10.x users: Update the Camel version property or dependency to 4.10.3
  4. 4. For Camel 4.8.x users: Update the Camel version property or dependency to 4.8.6
  5. 5. Rebuild the project to download the fixed versions
  6. 6. Run existing test suites to verify the upgrade does not break functionality
  7. 7. Redeploy the updated application

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Camel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30177 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30177 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data