# CVE-2024-8525: Automated Logic WebCTRL and Carrier i-Vu Unrestricted File Upload

> Unauthenticated attackers can upload malicious files to execute remote commands on Automated Logic WebCTRL and Carrier i-Vu systems.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Nov 2024
- **Updated:** 21 Nov 2024

## What is CVE-2024-8525?

CVE-2024-8525 is a critical vulnerability in Automated Logic, a Carrier company WebCTRL, published on 21 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unrestricted upload of file with dangerous type in Automated Logic WebCTRL 7.0 could allow an unauthenticated user to perform remote command execution via a crafted HTTP POST request which could lead to uploading a malicious file.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2024-8525 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8525 is a critical vulnerability in Automated Logic, a Carrier company WebCTRL, published on 21 Nov 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-8525 in the wild and no public exploit code.

Affected product: Automated Logic, a Carrier company WebCTRL. 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-8525/ (Markdown: https://insights.sbomify.com/CVE-2024-8525/index.md)
```

## Sources

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

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