Improper Input Validation during User Account Creation in Splunk Enterprise
Splunk Enterprise · Splunk Cloud Platform
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Cloud Platform |
|
Splunk Enterprise · Splunk Cloud Platform
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Cloud Platform |
|
≥ 10.1.2507 · < 10.1.2507.20≥ 10.0.2503 · < 10.0.2503.13≥ 9.3.2411 · < 9.3.2411.127| No fix yet |
In Splunk Enterprise versions below 10.2.2, 10.0.5, 9.4.10, and 9.3.11, and Splunk Cloud Platform versions below 10.4.2603.0, 10.3.2512.6, 10.2.2510.10, 10.1.2507.20, 10.0.2503.13, and 9.3.2411.127, a user who holds a role that contains the high-privilege capability `edit_user`could create a specially crafted username that includes a null byte or a non-UTF-8 percent-encoded byte due to improper input validation.<br><br>This could lead to inconsistent conversion of usernames into a proper format for storage and account management inconsistencies, such as being unable to edit or delete affected users.
From the CVE record · cisco
Splunk Enterprise and Splunk Cloud Platform improperly validate usernames. An authenticated user with a role containing the high-privilege `edit_user` capability can create a username containing a null byte or a non-UTF-8 percent-encoded byte, potentially making affected users impossible to edit or delete. The description does not specify a network or local access requirement or any victim interaction.
Teams running Splunk Enterprise below 10.2.2, 10.0.5, 9.4.10, or 9.3.11, or Splunk Cloud Platform below 10.4.2603.0, 10.3.2512.6, 10.2.2510.10, 10.1.2507.20, 10.0.2503.13, or 9.3.2411.127 should check their deployments.