Splunk App For Soar
Approved changes feed: RSS · Atom
cpe:2.3:a:splunk:splunk_app_for_soar:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Splunk (0f7ef08f-e3f5-59a4-ba5f-26afb7835b46) |
|---|---|
| Product | Splunk App For Soar (eefdfc01-089d-5474-abc9-a29f6707268e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-22621 |
vulnerable | 2026-06-03 14:59:40.978552 |
Privilege escalation for users who hold the “splunk_app_soar“ role in the Splunk App for SOAR
MEDIUM (6.4)
In versions 1.0.67 and lower of the Splunk App for SOAR, the Splunk documentation for that app recommended adding the `admin_all_objects` capability to the `splunk_app_soar` role. This addition could lead to improper access control for a low-privileged user that does not hold the "admin" Splunk roles.
Published: 2025-01-07T16:48:32.866Z
Updated: 2025-02-28T11:03:57.914Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.