CVE-2022-41923
A public proof of concept exists; no exploitation attested.
- Published2022-11-23
- Fixed in5.1.1 · 4.0.5 · 3.3.2
- WeaknessCWE-269 · CWE-863
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Grails Spring Security Core plugin is vulnerable to privilege escalation. The vulnerability allows an attacker access to one endpoint (i.e. the targeted endpoint) using the authorization requirements of a different endpoint (i.e. the donor endpoint). In some Grails framework applications, access to the targeted endpoint will be granted based on meeting the authorization requirements of the donor endpoint, which can result in a privilege escalation attack. This vulnerability has been patched in grails-spring-security-core versions 3.3.2, 4.0.5 and 5.1.1. Impacted Applications: Grails Spring Security Core plugin versions: 1.x 2.x >=3.0.0 <3.3.2 >=4.0.0 <4.0.5 >=5.0.0 <5.1.1 We strongly suggest that all Grails framework applications using the Grails Spring Security Core plugin be updated to a patched release of the plugin. Workarounds: Users should create a subclass extending one of the following classes from the `grails.plugin.springsecurity.web.access.intercept` package, depending on their security configuration: * `AnnotationFilterInvocationDefinition` * `InterceptUrlMapFilterInvocationDefinition` * `RequestmapFilterInvocationDefinition` In each case, the subclass should override the `calculateUri` method like so: ``` @Override protected String calculateUri(HttpServletRequest request) { UrlPathHelper.defaultInstance.getRequestUri(request) } ``` This should be considered a temporary measure, as the patched versions of grails-spring-security-core deprecates the `calculateUri` method. Once upgraded to a patched version of the plugin, this workaround is no longer needed. The workaround is especially important for version 2.x, as no patch is available version 2.x of the GSSC plugin.
Timeline
dates in UTC- 2022-11-2319:15CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-41923?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-41923?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 5.x | ≥ 5.0.0, < 5.1.1 | 5.1.1 | NVD |
| 4.0 | ≥ 4.0.0, < 4.0.5 | 4.0.5 | NVD |
| 3.3 | ≥ 1.0, < 3.3.2 | 3.3.2 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Grails spring security core to 5.1.1 · 4.0.5 · 3.3.2
Advisories and patches
- github.comMitigation
- github.comPatch
- grails.orgPatch · Vendor Advisory
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
Sources
- CISA-ADPSSVC decisionnone2025-04-23
- OpenCVESSVC decisionnone—
- CNACVSS 3.19.1read 2026-10-23
- NVDCVSS 3.19.8read 2026-10-23
- CNAweakness (CWE)CWE-269read 2026-10-23
- NVDweakness (CWE)CWE-863read 2026-10-23
- FIRST EPSSEPSS score1.9 %2026-10-23
- PoC-in-GitHubproof of concept1read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2022-11-23
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2022-41923?
Is CVE-2022-41923 actively exploited?
What is the CVSS score for CVE-2022-41923?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.