cve.bz

CVE-2024-58398 coder coder: Open Redirect

5.3 mediumEPSS 0.3%Fix available

Medium (5.3) in coder coder. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/coder/coder/v2 2.14.4, 2.15.3, 2.16.1.

On this page
Coder 2.3.1 before 2.14.4, 2.15.x before 2.15.3, and 2.16.0 before 2.16.1 contains an open redirect vulnerability in the login page because the redirect query parameter is improperly sanitized. Attackers can craft a Coder login URL that, when clicked by a logged-in user, redirects the victim to an attacker-controlled website for phishing.

Severity

CVSS 4.0

5.3 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 19th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-601 URL Redirection to Untrusted Site (Open Redirect)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • github.com/coder/coder/v2 (Go): fixed in 2.16.1, 2.15.3, 2.14.4

Ask an AI about this CVE

Show the promptExplain CVE-2024-58398 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-58398?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-58398?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-58398 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
coderfrom 2.16.0 before 2.16.1
coderfrom 2.15.0 before 2.15.3
coderfrom 2.3.1 before 2.14.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-wcx9-ccpj-hx3cGogithub.com/coder/coder/v2>=2.16.0 <2.16.12.16.1
GHSA-wcx9-ccpj-hx3cGogithub.com/coder/coder/v2>=2.15.0 <2.15.32.15.3
GHSA-wcx9-ccpj-hx3cGogithub.com/coder/coder/v2>=2.3.1 <2.14.42.14.4
GO-2024-3228Gogithub.com/coder/coderall versionsno fix published
GO-2024-3228Gogithub.com/coder/coder/v2>=2.3.1 <2.14.4
>=2.15.0 <2.15.3
>=2.16.0 <2.16.1
2.14.4, 2.15.3, 2.16.1

Attack patterns (CAPEC)

  • CAPEC-178 Cross-Site Flashing Likelihood: Medium · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON