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.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:HSplunk
APPSplunk9.3.0 – 9.3.11 (excl.)9.4.0 – 9.4.10 (excl.)10.0.0 – 10.0.5 (excl.)10.2.0 – 10.2.2 (excl.)Splunk Cloud Platform
APPSplunk9.3.2411 – 9.3.2411.127 (excl.)10.0.2503 – 10.0.2503.13 (excl.)10.1.2507 – 10.1.2507.20 (excl.)10.2.2510 – 10.2.2510.10 (excl.)10.3.2512 – 10.3.2512.6 (excl.)
Related vulnerabilities
Splunk Enterprise — tworzenie/skracanie plików bez uwierzytelnienia przez sidecar PostgreSQL
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who has an emb...
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who has an emb...
In Splunk Enterprise versions below 10.4.1, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who can read t...
Splunk Enterprise: RCE przez deployment server na wszystkich Universal Forwarder