# CVE-2024-36416: SuiteCRM v4 API Excessive log data DOS

> Attackers can cause denial of service in SuiteCRM by exploiting a deprecated v4 API that logs excessive data without rotation.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2024
- **Updated:** 13 Feb 2025
- **Also known as:** BIT-suitecrm-2024-36416, GHSA-jrpp-22g3-2j77

## What is CVE-2024-36416?

CVE-2024-36416 is a high-severity denial of service vulnerability in Salesagility Suitecrm, published on 10 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SuiteCRM is an open-source Customer Relationship Management (CRM) software application. Prior to versions 7.14.4 and 8.6.1, a deprecated v4 API example with no log rotation allows denial of service by logging excessive data. Versions 7.14.4 and 8.6.1 contain a fix for this issue.

Weakness: CWE-779 (Logging of Excessive Data)

## Which versions are affected by CVE-2024-36416?

1 open source package ship an affected version, including suitecrm. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `suitecrm` | Bitnami | All versions | 7.14.4, 8.6.1 |

Products: Salesagility Suitecrm.

## How do I fix CVE-2024-36416?

Upgrade suitecrm to a fixed version for your release line: 7.14.4 or 8.6.1.

## Is CVE-2024-36416 being exploited?

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

Public exploit code:

- Tool for validating / testing CVE-2024-36416 (github_poc): https://github.com/kva55/CVE-2024-36416

## Other vulnerabilities in Salesagility Suitecrm

- [CVE-2024-36412](https://insights.sbomify.com/CVE-2024-36412/): SuiteCRM unauthenticated SQL Injection (critical 10.0)
- [CVE-2024-1644](https://insights.sbomify.com/CVE-2024-1644/): Suite CRM v7.14.2 - RCE via Local File Inclusion (critical 9.9)
- [CVE-2021-45898](https://insights.sbomify.com/CVE-2021-45898/): Path traversal in n/a (critical 9.8)
- [CVE-2021-45899](https://insights.sbomify.com/CVE-2021-45899/): Deserialization in n/a (critical 9.8)
- [CVE-2020-8783](https://insights.sbomify.com/CVE-2020-8783/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36416 and fix it if it is affected.

What it is: CVE-2024-36416 is a high-severity denial of service vulnerability in Salesagility Suitecrm, published on 10 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-36416 in the wild and no public exploit code.

Affected packages and fixed versions:
- suitecrm (Bitnami): affected all versions; fixed in 7.14.4, 8.6.1

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-2024-36416/ (Markdown: https://insights.sbomify.com/CVE-2024-36416/index.md)
```

## Sources

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

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