Skip to content

[Snyk] Security upgrade org.apache.maven.wagon:wagon-http-lightweight from 3.2.0 to 3.5.3 - #47

Open
ecki wants to merge 1 commit into
karaf-4.2.x-seeburgerfrom
snyk-fix-a8e3876f444b2d03e08a021479d2e907
Open

ecki wants to merge 1 commit into
karaf-4.2.x-seeburgerfrom
snyk-fix-a8e3876f444b2d03e08a021479d2e907

Conversation

@ecki

@ecki ecki commented Oct 4, 2024

Copy link
Copy Markdown
Member

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

  • pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue Score Upgrade
medium severity Uncontrolled Resource Consumption
SNYK-JAVA-COMMONSIO-8161190
  631   org.apache.maven.wagon:wagon-http-lightweight:
3.2.0 -> 3.5.3
No Known Exploit

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Uncontrolled Resource Consumption

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JAVA-COMMONSIO-8161190
MrEasy pushed a commit that referenced this pull request Sep 16, 2026
* fix(management): apply the JMX RBAC guard to MBean lifecycle operations

The KarafMBeanServerGuard only intercepted invoke, getAttribute(s) and
setAttribute(s). createMBean, registerMBean and unregisterMBean went
straight to the delegate MBeanServer, so they were not subject to any
role check and behaved inconsistently with the rest of the guarded API.

Route these three operations through the guard as well:

* MBeanInvocationHandler adds them to the guarded operation list.
* KarafMBeanServerGuard resolves the required roles from the jmx.acl*
  configuration by ObjectName and operation name (the target MBean is
  not, or not yet, registered so no MBeanInfo introspection is done).
  For createMBean/registerMBean the class name is passed as the
  operation argument so ACL rules can match on it, e.g.
  createMBean(java.lang.String)[/javax\.management\.loading\..*/] = admin
* A null ObjectName falls back to the generic jmx.acl configuration.
* The default jmx.acl.cfg maps createMBean/registerMBean/unregisterMBean
  to the admin role (the existing "* = admin" already covered them).

* Fix Javadoc comment prematurely terminated by regex example

The ACL regex example in the handleRegistration Javadoc contained the
literal sequence */ (from \..*/]), which closed the block comment early
and broke compilation of org.apache.karaf.management.server. Escape the
trailing slash as / so the comment terminates where intended.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017MZQYyrYzSQHdHeD6AEGXT

---------

Co-authored-by: Jean-Baptiste Onofré <jbonofre@MacBookAir.local>
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants