dbcve.org
ManifoldcfApplication · Apache

CVE-2022-45910

MEDIUM · 5.3 CVSS v3.1 Published 2022-12-07
Fix available
A fix is available. Upgrade to after 2.23 or later.
See remediation →
62/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
Improper neutralization of special elements used in an LDAP query ('LDAP Injection') vulnerability in ActiveDirectory and Sharepoint ActiveDirectory authority connectors of Apache ManifoldCF allows an attacker to manipulate the LDAP search queries (DoS, additional queries, filter manipulation) during user lookup, if the username or the domain string are passed to the UserACLs servlet without validation. This issue affects Apache ManifoldCF version 2.23 and prior versions.

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

LDAP injection vulnerability in Apache ManifoldCF's ActiveDirectory and SharePoint connectors. The UserACLs servlet uses user-supplied username and domain string values in LDAP search queries without validation, allowing attackers to manipulate LDAP query parameters to cause DoS, execute additional queries, or modify LDAP filters.

MitigationImplement strict input validation and proper LDAP special character escaping/parameterization for all user-supplied values (username and domain) before constructing LDAP search queries in the UserACLs servlet.

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
ManifoldcfApplication
Affected:<= 2.23

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 ManifoldCF installation and version
    Locate the ManifoldCF installation directory and check the version file or manifest (typically found in the root installation folder or packaged with the distribution). Compare the installed version to the affected range: versions <= 2.23.
    Affected if The installed version of Apache ManifoldCF is 2.23 or lower.
  2. Verify UserACLs servlet is accessible
    Check if the UserACLs endpoint is exposed in the web application. This servlet typically handles ACL operations for ActiveDirectory and SharePoint connectors.
    Affected if The UserACLs servlet is accessible and accepts user-supplied username and domain parameters.
  3. Confirm ActiveDirectory connector is configured
    Inspect the ManifoldCF configuration for ActiveDirectory repository connections. Look for configured AD authority connections in the connections configuration file or database.
    Affected if An ActiveDirectory connector is configured and active in the ManifoldCF environment.
  4. Confirm SharePoint connector is configured
    Inspect the ManifoldCF configuration for SharePoint repository connections. Look for configured SharePoint authority connections in the connections configuration file or database.
    Affected if A SharePoint connector is configured and active in the ManifoldCF environment.

A user is affected if they are running Apache ManifoldCF version 2.23 or lower with the UserACLs servlet accessible and either ActiveDirectory or SharePoint connectors configured and 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 a release after 2.23
Interim mitigation

Implement strict input validation and proper LDAP special character escaping/parameterization for all user-supplied values (username and domain) before constructing LDAP search queries in the UserACLs servlet.

Recommended fix Moderate confidence

Apache ManifoldCF 2.24 or latest stable release

  1. 1. Download Apache ManifoldCF version 2.24 or later from the official Apache repository (https://manifoldcf.apache.org/)
  2. 2. Review the release notes for version 2.24 to confirm the LDAP injection vulnerability (CVE-2022-45910) is addressed
  3. 3. Back up your current ManifoldCF configuration and database
  4. 4. Stop the ManifoldCF service
  5. 5. Install the new version (2.24 or latest stable)
  6. 6. Restore your configuration from the backup
  7. 7. Start the ManifoldCF service
  8. 8. Test the ActiveDirectory and Sharepoint ActiveDirectory authority connectors to verify the fix is working
Caveat Review release notes for any configuration or API changes between 2.23 and the target version; minor version upgrades in Apache ManifoldCF typically maintain backward compatibility

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

Fix this in Manifoldcf Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45910 — 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-2022-45910 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