org.apache.karaf.management:org.apache.karaf.management.server@4.1.0 vulnerabilities
-
latest version
4.4.5
-
latest non vulnerable version
-
first published
13 years ago
-
latest version published
4 months ago
-
licenses detected
- [2.2.4,)
-
package manager
Direct Vulnerabilities
Known vulnerabilities in the org.apache.karaf.management:org.apache.karaf.management.server package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.Vulnerability | Vulnerable Version |
---|---|
org.apache.karaf.management:org.apache.karaf.management.server is a package that bundles starts the Karaf embedded MBean server and RMI registry allowing users to use JMX to manage Karaf. Affected versions of this package are vulnerable to Deserialization of Untrusted Data due to a lack of implementation used by Apache Karaf for such attacks. Note: Karaf uses a limited set of classes in the JMX server class path. How to fix Deserialization of Untrusted Data? Upgrade |
[,4.3.6)
|
org.apache.karaf.management:org.apache.karaf.management.server is a package that bundles starts the Karaf embedded MBean server and RMI registry allowing users to use JMX to manage Karaf. Affected versions of this package are vulnerable to Access Restriction Bypass. 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. How to fix Access Restriction Bypass? Upgrade |
[,4.2.8)
|