Kroxylicious-authorizer-acl: kroxylicious: acl rule file regex escapes are stripped, broadening 'matching' authorization rules
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions |
|---|---|---|---|
| Red Hat | streams for Apache Kafka 3 | affected | — |
No data.
No data.
No data available yet.
Vendor Workaround
Until a fixed release is available, write regex escapes with doubled backslashes (for example `/orders\\.v1/`), audit existing `matching` rules for unintended matches, and prefer exact or `like` predicates where regex matching is not required.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in Kroxylicious. The ACL authorizer's rules-file parser unquotes `matching /…/` regular-expression literals using the string unquoting rules, which strips every backslash escape. As a result, an allow rule such as `matching /orders\.v1/` is compiled as the regex `orders.v1`, which also matches unintended names such as `ordersXv1`, and character classes such as `\d` and `\w` lose their special meaning. Allow rules written with regex escapes can therefore apply to more resources than the author intended. Depending on the ACL configuration, this may allow an authenticated Kafka client to access a resource (such as read or write a topic) that should have been denied. | |
| Title | Kroxylicious-authorizer-acl: kroxylicious: acl rule file regex escapes are stripped, broadening 'matching' authorization rules | |
| First Time appeared |
Redhat
Redhat amq Streams |
|
| Weaknesses | CWE-863 | |
| CPEs | cpe:/a:redhat:amq_streams:3 | |
| Vendors & Products |
Redhat
Redhat amq Streams |
|
| References |
| |
| Metrics |
cvssV3_1
|