Flagr before 1.2.5 Authentication Bypass via Default Basic-Auth Whitelist
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| OpenFlagr | Flagr | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Openflagr | Flagr |
|
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 |
|---|---|---|
| First Time appeared |
Openflagr
Openflagr flagr |
|
| Vendors & Products |
Openflagr
Openflagr flagr |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Flagr before 1.2.5 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to access the flag management write API through an insecure default FLAGR_BASIC_AUTH_WHITELIST_PATHS including /api/v1/flags. Because basicAuth.whitelist() in pkg/config/middleware.go matches only path prefixes regardless of HTTP method, attackers can create, modify, enable, disable, and delete flags, variants, segments, constraints, and distributions. | |
| Title | Flagr before 1.2.5 Authentication Bypass via Default Basic-Auth Whitelist | |
| Weaknesses | CWE-1188 | |
| References |
|
|
| Metrics |
cvssV3_1
|