# CVE-2024-21497: Open Redirect in github.com/greenpau/caddy-security

> Attackers can trick users into visiting malicious sites via crafted URLs in the Caddy security plugin, facilitating phishing attacks.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N/E:P`)
- **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:** 17 Feb 2024
- **Updated:** 3 Mar 2026
- **Also known as:** GHSA-8hp3-rmr7-xh88, GO-2024-2560

## What is CVE-2024-21497?

CVE-2024-21497 is a medium-severity vulnerability in github.com/greenpau/caddy-security, published on 17 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

Versions of the package github.com/greenpau/caddy-security  are vulnerable to Open Redirect via the redirect_url parameter. An attacker could perform a phishing attack and trick users into visiting a malicious website by crafting a convincing URL with this parameter. To exploit this vulnerability, the user must take an action, such as clicking on a portal button or using the browser’s back button, to trigger the redirection.

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

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

3 open source packages ship an affected version, including github.com/greenpau/caddy-security. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/greenpau/caddy-security` | Go | All versions | None |
| `github.com/greenpau/caddy-security` | Go | All versions to 1.1.23 | None |
| `github.com/greenpau/caddy-security` | Go | All versions to 1.1.23 | None |

Products: Greenpau Caddy-Security.

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

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

## Is CVE-2024-21497 being exploited?

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

## Other vulnerabilities in github.com/greenpau/caddy-security

- [CVE-2024-21495](https://insights.sbomify.com/CVE-2024-21495/): Use of Insufficiently Random Values in github.com/greenpau/caddy-security (medium 6.5)
- [CVE-2024-21494](https://insights.sbomify.com/CVE-2024-21494/): Authentication Bypass by Spoofing in github.com/greenpau/caddy-security (medium 5.4)
- [CVE-2024-21493](https://insights.sbomify.com/CVE-2024-21493/): Improper Validation of Array Index in github.com/greenpau/caddy-security (medium 5.3)
- [CVE-2024-21499](https://insights.sbomify.com/CVE-2024-21499/): Improper Neutralization of HTTP Headers in github.com/greenpau/caddy-security (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-21497 is a medium-severity vulnerability in github.com/greenpau/caddy-security, published on 17 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-21497 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/greenpau/caddy-security (Go): affected all versions; no fix listed
- github.com/greenpau/caddy-security (Go): affected all versions up to 1.1.23; no fix listed
- github.com/greenpau/caddy-security (Go): affected all versions up to 1.1.23; no fix listed

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

## Sources

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

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