CVE-2024-45247
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSonarr – CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSonarr contains an open redirect vulnerability (CWE-601) where the application does not properly validate redirect targets before forwarding users to another site. An attacker can craft a malicious URL appearing to originate from the Sonarr server that redirects victims to an arbitrary external site, potentially facilitating phishing or credential theft attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Sonarr installation and versionCheck your system for Sonarr installation. Common methods: look for running service (systemctl status sonarr), check installed packages, or access the web UI and view the version information typically found in System > About or the footer of the interface.Affected if The installed version is any version of Sonarr that contains the vulnerable redirect handling code and has the web interface accessible.
-
Locate the redirect endpointIdentify URL patterns in Sonarr that handle redirection. Common redirect patterns include parameters like 'returnUrl', 'redirect', 'url', or 'go' in query strings. Review web server logs or application traces for requests containing redirect-related parameters.Affected if Your Sonarr instance exposes any web endpoints accepting redirect parameters that forward users to other pages.
-
Test redirect target validationCraft a test URL using your Sonarr base URL with a redirect parameter pointing to an external domain (for example: https://your-sonarr-url/?redirect=https://malicious-example.com). Submit the request and observe whether the application blocks, sanitizes, or allows the external redirect.Affected if The application accepts and follows redirects to arbitrary external domains without blocking or validating that the target is a relative/internal path.
-
Inspect redirect handling code or configurationIf you have access to Sonarr configuration files or logs, examine the redirect handling logic. Look for settings that control URL validation, whitelist patterns for allowed redirect domains, or any proxy/rewrite rules that might affect redirect behavior.Affected if No strict domain whitelist is configured, or the validation logic permits any URL scheme or external domain in redirect parameters.
Your environment is affected if Sonarr is running with a web interface and accepts redirect parameters that can be manipulated to forward users to arbitrary external URLs without proper validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict validation of all redirect parameters to ensure they point only to trusted, relative paths or explicitly allowed domains. Reject or sanitize any redirect targets containing untrusted external URLs or suspicious patterns.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45247 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-45247 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data