In Eclipse Jetty, across various versions of `jetty-annotations`, and `jetty-eeN-annotations`, the Jakarta Spec authoritative url-pattern ru
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- org.eclipse.jetty.ee11:jetty-ee11-annotations
From 12.1.0 · through 12.1.11
- org.eclipse.jetty.ee10:jetty-ee10-annotations
From 12.1.0 · through 12.1.11; From 12.0.0 · through 12.0.38
- org.eclipse.jetty.ee9:jetty-ee9-annotations
From 12.1.0 · through 12.1.11; From 12.0.0 · through 12.0.38
- org.eclipse.jetty.ee8:jetty-ee8-annotations
From 12.1.0 · through 12.1.11; From 12.0.0 · through 12.0.38
- org.eclipse.jetty:jetty-annotations
From 11.0.0 · through 11.0.32; From 10.0.0 · through 10.0.32; From 9.4.0 · through 9.4.64