Audit Log Injection through the REST API in Splunk Enterprise
概要
In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could inject arbitrary fields into Splunk Enterprise audit records via the Representational State Transfer (REST) API.
Successful exploitation could allow the unauthenticated user to forge audit evidenc...
影響パッケージ
| パッケージ | 影響を受ける版 → 修正版 | |
|---|---|---|
| SplunkSplunk Enterprise |
10.4 以上 10.4.5 未満→ 10.4.5 10.2 以上 10.2.9 未満→ 10.2.9 10.0 以上 10.0.12 未満→ 10.0.12 9.4 以上 9.4.17 未満→ 9.4.17 |
10.4.5 10.2.9 10.0.12 9.4.17 |
原文の説明 取得元が公開している説明をそのまま載せています (多くは英語)。
In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could inject arbitrary fields into Splunk Enterprise audit records via the Representational State Transfer (REST) API.
Successful exploitation could allow the unauthenticated user to forge audit evidence, compromising the integrity of audit reviews and security detections that rely on legacy audit-field parsing.
The vulnerability exists because Splunk Enterprise does not neutralize field delimiters in user-supplied data before writing the data to a legacy audit record. The affected workflow also does not create a corresponding structured audit record.
For more information see Auditing activities in a Splunk platform instance (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.0/audit-activity-in-splunk-enterprise/auditing-activities-in-a-splunk-platform-instance) and About structured audit trail logs (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/audit-activity-in-splunk-enterprise/about-structured-audit-trail-logs) in the Splunk documentation.
出典: CVE.org (CVE Program・cvelistV5) NVD
参照URL
- web psirt@cisco.com