# CVE-2024-8526: Automated Logic WebCTRL and Carrier i-Vu Open Redirect

> An attacker can redirect authenticated users to malicious sites via crafted URLs in WebCTRL and i-Vu, potentially facilitating phishing attacks.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 21 Nov 2024
- **Updated:** 21 Nov 2024

## What is CVE-2024-8526?

CVE-2024-8526 is a medium-severity vulnerability in Automated Logic, a Carrier company WebCTRL, published on 21 Nov 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

A vulnerability in Automated Logic WebCTRL 7.0 could allow an attacker to send a maliciously
crafted URL, which when visited by an authenticated WebCTRL user, could result in the redirection
of the user to a malicious webpage via "index.jsp"

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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


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

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

## Is CVE-2024-8526 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8526 is a medium-severity vulnerability in Automated Logic, a Carrier company WebCTRL, published on 21 Nov 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-8526 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-8526/ (Markdown: https://insights.sbomify.com/CVE-2024-8526/index.md)
```

## Sources

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

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