quarkus-openapi-generator has overly broad path-parameter matching that sends authentication headers to unintended operations
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.3epss 0.4%
exploitation probability
0.4%top 66% of all CVEs
observed exploitation
nono source reports it
Quarkus OpenAPI Generator is Quarkus' extensions for generation of Rest Clients and server stubs generation. Prior to versions 2.11.1-lts, 2.16.0-lts, and 2.17.0, the generated authentication filter matches OpenAPI path templates too broadly when deciding whether to attach credentials. A security scheme configured for one operation can therefore be applied to a different same-method operation whose path only partially resembles the protected template, causing bearer tokens, API keys, or basic credentials to be sent to unintended endpoints. This issue has been patched in versions 2.11.1-lts, 2.16.0-lts, and 2.17.0.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Affected products
quarkiverse · quarkus-openapi-generatorReferences
https://github.com/quarkiverse/quarkus-openapi-generator/pull/1586https://github.com/quarkiverse/quarkus-openapi-generator/releases/tag/2.11.1-ltshttps://github.com/quarkiverse/quarkus-openapi-generator/releases/tag/2.16.0-ltshttps://github.com/quarkiverse/quarkus-openapi-generator/releases/tag/2.17.0https://github.com/quarkiverse/quarkus-openapi-generator/security/advisories/GHSA-fr8f-rwjx-f32v