# CVE-2025-0367: Regular Expression Denial of Service (ReDoS) in Splunk Supporting Add-on for Active Directory (SA-ldapsearch)

> Attackers can cause a denial of service in Splunk's Active Directory add-on via a vulnerable regular expression pattern.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jan 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-xrrm-r8x3-wh4p

## What is CVE-2025-0367?

CVE-2025-0367 is a medium-severity denial of service vulnerability in Splunk Supporting Add-on for Active Directory, published on 30 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In versions 3.1.0 and lower of the Splunk Supporting Add-on for Active Directory, also known as SA-ldapsearch, a vulnerable regular expression pattern could lead to a Regular Expression Denial of Service (ReDoS) attack.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2025-0367?


## How do I fix CVE-2025-0367?

No fix has been published for CVE-2025-0367 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-0367 being exploited?

There is no known exploitation of CVE-2025-0367 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0367 and fix it if it is affected.

What it is: CVE-2025-0367 is a medium-severity denial of service vulnerability in Splunk Supporting Add-on for Active Directory, published on 30 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0367 in the wild and no public exploit code.

Affected product: Splunk Supporting Add-on for Active Directory. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-0367/ (Markdown: https://insights.sbomify.com/CVE-2025-0367/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-0367
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-0367
- OSV: https://osv.dev/vulnerability/CVE-2025-0367

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-0367/
Summaries are generated and may contain mistakes; the official description above is the record.