Improper Input Validation of Timestamps through the REST API in Splunk SOAR
Summary
In Splunk SOAR versions below 8.8.0, a user with container edit permission could supply timestamps when creating containers and artifacts through the Representational State Transfer (REST) API. This could alter the timeline shown to analysts and cause configured data retention strategies to delete a...
Affected packages
| Package | Affected → Fixed | |
|---|---|---|
| SplunkSplunk SOAR |
< 8.8.0→ 8.8.0 |
8.8.0 |
Original description The description as published by the source.
In Splunk SOAR versions below 8.8.0, a user with container edit permission could supply timestamps when creating containers and artifacts through the Representational State Transfer (REST) API. This could alter the timeline shown to analysts and cause configured data retention strategies to delete affected records earlier than intended.
The vulnerability is possible because the REST API accepts client-supplied values for timestamps that Splunk SOAR uses to order records and apply data retention.
The early deletion impact requires an applicable data retention strategy; the timeline impact does not.
For more information see Manage your PostgreSQL database with data retention strategies (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/6.4.0/manage-your-splunk-soar-on-premises-system-health-and-performance/manage-your-postgresql-database-with-data-retention-strategies) in the Splunk documentation.
Source: CVE.org (CVE Program・cvelistV5) NVD
References
- web psirt@cisco.com