Authorization Bypass via Mixed @ServletSecurity and web.xml Constraints in Eclipse Jetty
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Eclipse Foundation | unaffected |
|
|||||||||||||
| Eclipse Foundation | unaffected |
|
|||||||||||||
| Eclipse Foundation | unaffected |
|
|||||||||||||
| Eclipse Foundation | unaffected |
|
|||||||||||||
| Eclipse Foundation | unaffected |
|
No data.
No data.
No data available yet.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.424% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Authorization Bypass via Mixed @ServletSecurity and web.xml Constraints in Eclipse Jetty |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Eclipse Jetty, across various versions of `jetty-annotations`, and `jetty-eeN-annotations`, the Jakarta Spec authoritative url-pattern rules for mixed `@ServletSecurity` annotation, and `web.xml` defined `security-constraint` on the same `url-pattern` were not being applied if the `web.xml` had more than 1 `url-pattern` for a servlet, and had a `security-constraint` applying to only some of those `url-pattern` definitions. | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV4_0
|
No data.