dbcve.org
KarafApplication · Apache

CVE-2022-22932

MEDIUM · 5.3 CVSS v3.1 Published 2022-01-26
Fix available
A fix is available. Upgrade to 4.2.15 / 4.3.6 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
Apache Karaf obr:* commands and run goal on the karaf-maven-plugin have partial path traversal which allows to break out of expected folder. The risk is low as obr:* commands are not very used and the entry is set by user. This has been fixed in revision: https://gitbox.apache.org/repos/asf?p=karaf.git;h=36a2bc4 https://gitbox.apache.org/repos/asf?p=karaf.git;h=52b70cf Mitigation: Apache Karaf users should upgrade to 4.2.15 or 4.3.6 or later as soon as possible, or use correct path. JIRA Tickets: https://issues.apache.org/jira/browse/KARAF-7326

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

Apache Karaf contains a partial path traversal vulnerability in the obr:* commands and the run goal of karaf-maven-plugin. An attacker can break out of the expected folder by using path traversal sequences in commands that should be confined to a specific directory.

MitigationUpgrade Apache Karaf to version 4.2.15 or 4.3.6 or later, or ensure proper path validation is applied when using obr:* commands.

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
KarafApplication
Affected:< 4.2.15>= 4.3.0, < 4.3.6

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Karaf installation version
    Check the Karaf version by examining the lib/karaf-*.jar file in the Karaf installation directory, or run 'karaf --version' from the command line if accessible
    Affected if The installed version is less than 4.2.15, or greater than or equal to 4.3.0 but less than 4.3.6
  2. Locate ObrCommand implementation files
    Search for Java source files containing 'ObrCommand' class definitions in the Karaf source or check for obr related command classes in the org.apache.karaf.obr.core bundle if the source is available
    Affected if ObrCommand classes exist in the deployment, indicating obr:* commands are available
  3. Identify karaf-maven-plugin usage
    Search project pom.xml files for references to 'karaf-maven-plugin' and examine whether the 'run' goal is configured in the plugin section
    Affected if The karaf-maven-plugin is configured with the run goal in any pom.xml within the project
  4. Review shell script or automation using obr commands
    Examine any shell scripts, CI/CD pipelines, or automation that invoke 'obr:*' commands such as obr:url, obr:list, or obr:install
    Affected if Scripts or automation invoke obr commands which accept URLs or resource paths as arguments
  5. Check for path traversal patterns in obr configurations
    Review any obr URL configuration files or command arguments that might accept file paths and could contain '..' sequences
    Affected if Obr configurations accept user-controlled paths that are not validated against path traversal

You are affected if you run Apache Karaf versions below 4.2.15 or between 4.3.0 and 4.3.5, and you use obr:* commands or the run goal of karaf-maven-plugin with untrusted or user-supplied paths.

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.2.15 / 4.3.6 or later
Fixed in 4.2.154.3.6
Interim mitigation

Upgrade Apache Karaf to version 4.2.15 or 4.3.6 or later, or ensure proper path validation is applied when using obr:* commands.

Recommended fix High confidence

4.2.15 or 4.3.6 (or later)

  1. Identify your current Apache Karaf version by checking the Karaf release or pom.xml
  2. If using Karaf 4.2.x, upgrade to version 4.2.15 or later
  3. If using Karaf 4.3.x, upgrade to version 4.3.6 or later
  4. Verify the upgrade by checking that the path traversal vulnerability in obr:* commands and karaf-maven-plugin is resolved
  5. Test the upgraded Karaf instance to ensure normal operation

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

Fix this in Karaf Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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