<!--This ticket is confidential.--> <!--############################# Do not remove the lines above #############################--> # CVE Reservation Request <!--There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#vulnerability-cve Note that this issue is configured (see the quick actions at the bottom) to be created as confidential. Note that a vulnerability does not need to actually be resolved before it is reported and that these reports can be revised as needed (reopen the issue to request changes). If you do not know how to fill certain fields, mark that in the comment and we will help you. You can delete the comments (or not).--> The Eclipse Foundation is a [Common Vulnerabilities and Exposures](https://cve.mitre.org/) (CVE) Numbering Authority. Creating this ticket initiates **reservation** of a CVE ID for the documented vulnerability. The reserved CVE ID will be posted in a comment below, and kept **confidential** until explicit publication request. > [!note] > > To request CVE _publication_, please open a [CVE publication](https://gitlab.eclipse.org/security/cve-assignment/-/issues/new?issuable_template=CVE%20Publication%20Request&issue%5Bconfidential%5D=true) ticket. Please fill in the fields below to draft the CVE record. --- <!--Required. Specify the project's name (e.g., "Eclipse Dash") and Eclipse Foundation ID, e.g., "technology.dash".--> ## CVE record information **Project name:** Eclipse Vert.x **Project id:** rt.vertx **Versions affected:** \[4.0.0, 4.5.34\] or \[5.0.0,5.0.12\] or \[5.1.0,5.1.9\] or \[5.2.0, 5.2.0\] **Common Vulnerability Scoring System:** CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N **Summary:** In Eclipse Vert.x versions \[4.0.0, 4.5.34\] or \[5.0.0,5.0.12\] or \[5.1.0,5.1.9\] or \[5.2.0, 5.2.0\], a scope bypass vulnerability exists in Eclipse Vert.x Web's ChainAuthHandler when used with scope-requiring authentication handlers such as JWTAuthHandler or OAuth2AuthHandler. When a user is already authenticated on the routing context by a preceding handler in the request pipeline, ChainAuthHandler skips all scope validation configured via withScope() or withScopes(). This affects both any() and all() chain modes. The root cause is that postAuthentication() relies on internal state that is only set during the authenticate() phase, which is skipped entirely for pre-authenticated users. In any() mode, the absence of this state causes the method to fall through without delegating scope checks to any handler. In all() mode, scope checks are unconditionally skipped. This allows a user with a valid token but insufficient scopes to access resources protected by scope requirements, provided they were authenticated by an earlier handler in the pipeline. The most common trigger is overlapping authentication handlers on nested routes, where a parent route authenticates broadly and a child route uses a chain to enforce specific scopes. The impacted component Maven coordinate is io.vertx:vertx-web **Links:** https://github.com/vert-x3/vertx-web/security/advisories/GHSA-2p39-cr56-w58j **Credits:** Thomas Segismont.