# CVE-2024-1889: Cross-Site Request Forgery vulnerability in SMA Cluster Controller

> An attacker can trick authenticated users into performing unauthorized actions on the SMA Cluster Controller via a malicious link.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Feb 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-rg8h-4g25-hj75

## What is CVE-2024-1889?

CVE-2024-1889 is a high-severity vulnerability in SMA Cluster Controller, published on 26 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-Site Request Forgery vulnerability in SMA Cluster Controller, affecting version 01.05.01.R. This vulnerability could allow an attacker to send a malicious link to an authenticated user to perform actions with these user permissions on the affected device.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 2 products.


Products: Sma Clcon-10 Firmware, Sma Clcon-S-10 Firmware.

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

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

## Is CVE-2024-1889 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1889 is a high-severity vulnerability in SMA Cluster Controller, published on 26 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-1889 in the wild and no public exploit code.

Affected product: SMA Cluster Controller. 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-2024-1889/ (Markdown: https://insights.sbomify.com/CVE-2024-1889/index.md)
```

## Sources

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

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