CVE-2024-23639

Enabled but unsecured management endpoints are susceptible to drive-by localhost attacks. While not typical of a production application, these attacks may have more impact on a development environment where such endpoints may be flipped on without much thought.

Details

A malicious/compromised website can make HTTP requests to localhost. Normally, such requests would trigger a CORS preflight check which would prevent the request; however, some requests are "simple" and do not require a preflight check. These endpoints, if enabled and not secured, are vulnerable to being triggered.

Production environments typically disable unused endpoints and secure/restrict access to needed endpoints. A more likely victim is the developer in their local development host, who has enabled endpoints without security for the sake of easing development.

CVE-2024-23639 has a CVSS score of 5.1 (Medium). The vector is requires local access, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.8.3); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2024-23639? CVE-2024-23639 is a medium-severity security vulnerability in io.micronaut:micronaut-http-server (maven), affecting versions < 3.8.3. It is fixed in 3.8.3.
2. How severe is CVE-2024-23639? CVE-2024-23639 has a CVSS score of 5.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2024-23639?
   • io.micronaut:micronaut-http-server (maven) (versions < 3.8.3)
   • io.micronaut:micronaut-http-server-netty (maven) (versions < 3.8.3)
   • io.micronaut:micronaut-http-server-tck (maven) (versions < 3.8.3)
4. Is there a fix for CVE-2024-23639? Yes. CVE-2024-23639 is fixed in 3.8.3. Upgrade to this version or later.
5. Is CVE-2024-23639 exploitable, and should I be worried? Whether CVE-2024-23639 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-23639 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-23639?
   • Upgrade io.micronaut:micronaut-http-server to 3.8.3 or later
   • Upgrade io.micronaut:micronaut-http-server-netty to 3.8.3 or later
   • Upgrade io.micronaut:micronaut-http-server-tck to 3.8.3 or later

Other vulnerabilities in io.micronaut:micronaut-http-server