How severe is CVE-2022-45046?

CVE-2022-45046 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-45046?

CVE-2022-45046 affects the following packages: org.apache.camel:camel-ldap (Maven), org.apache.camel:camel-ldap (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-45046?

Update org.apache.camel:camel-ldap to 3.14.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-45046 is resolved across your whole dependency graph.

How do I detect CVE-2022-45046 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.camel:camel-ldap, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-45046 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2022-45046?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-45046 can be triaged on real exposure rather than presence alone.

Is CVE-2022-45046 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-45046 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was CVE-2022-45046 published, and has it been updated?

CVE-2022-45046 was published on December 5, 2022 and was last updated on November 29, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Withdrawn — this advisory has been retracted

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

CVE-2022-45046 — camel-ldap

CRITICAL

CVE-2022-45046 is a critical-severity (CVSS 9.8) vulnerability in org.apache.camel:camel-ldap. A fix is available for org.apache.camel:camel-ldap — see the affected versions and patch details below.

camel-ldap component allows LDAP Injection when using the filter option

Also known asGHSA-w66j-xc7r-m2jv

Published

Dec 5, 2022

Updated

Nov 29, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 29, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

☕org.apache.camel:camel-ldap☕org.apache.camel:camel-ldap

Real-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

The camel-ldap component allows LDAP Injection when using the filter option. Users are recommended to either move to the Camel-Spring-Ldap component (which is not affected) or upgrade to 3.14.6 or 3.18.4.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.camel:camel-ldap`	all versions	3.14.6`org.apache.camel:camel-ldap:3.14.6`
☕Maven	`org.apache.camel:camel-ldap`	≥ 3.15.0&&< 3.18.4	3.18.4`org.apache.camel:camel-ldap:3.18.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.camel:camel-ldap, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.camel:camel-ldap to 3.14.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-45046 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-45046 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2022-45046. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-45046 in your dependencies?

O3 Security finds CVE-2022-45046 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works