Skip to content
Fencer Intel
medium 6.3

CVE-2020-11980 json

Server-Side Request Forgery in Karaf

published 6y ago modified 4mo ago also GHSA-9jg9-6wm2-x7p5 , EUVD-2022-0940

cvss
6.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits
0
none known

Summary

In Karaf, JMX authentication takes place using JAAS and authorization takes place using ACL files. By default, only an "admin" can actually invoke on an MBean. However there is a vulnerability there for someone who is not an admin, but has a "viewer" role. In the 'etc/jmx.acl.cfg', such as role can call get*. It's possible to authenticate as a viewer role + invokes on the MLet getMBeansFromURL method, which goes off to a remote server to fetch the desired MBean, which is then registered in Karaf. At this point the attack fails as "viewer" doesn't have the permission to invoke on the MBean. Still, it could act as a SSRF style attack and also it essentially allows a "viewer" role to pollute the MBean registry, which is a kind of privilege escalation. The vulnerability is low as it's possible to add a ACL to limit access. Users should update to Apache Karaf 4.2.9 or newer.

Patch / fix

  • maven org.apache.karaf.management:org.apache.karaf.management.server 4.2.9
  • apache karaf 4.2.9

Is CVE-2020-11980 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-11980 updated cvss 8.8

karaf: A remote client could create MBeans from arbitrary URLs

  • Red Hat OpenStack Platform 10 (Newton) opendaylight Red Hat OpenStack Platform 13 (Queens) opendaylight
    affected: workaround, no fix planned “It's possible to add a JMX ACL in etc configuration to limit access.”
  • Red Hat Fuse 7.8.0
    fixed: vendor fix “It's possible to add a JMX ACL in etc configuration to limit access.” RHSA-2020:5568
  • Red Hat Decision Manager 7 Karaf Karaf Red Hat Integration Camel K 1 Karaf Karaf Red Hat Process Automation 7 Karaf Karaf
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.88% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 6.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P
GitHub 3.1 6.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
maven org.apache.karaf.management:org.apache.karaf.management.server
<4.2.9
4.2.9

Affected products

  • n/a Apache Karaf

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.