CVE-2024-23639
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 · uneditedMicronaut Framework is a modern, JVM-based, full stack Java framework designed for building modular, easily testable JVM applications with support for Java, Kotlin and the Groovy language. 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. 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. This issue has been addressed in version 3.8.3. Users are advised to upgrade.
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 · high confidenceMicronaut Framework versions before 3.8.3 have unsecured management endpoints vulnerable to drive-by localhost attacks. Malicious websites can exploit cross-origin 'simple' requests that bypass CORS preflight checks to trigger these endpoints, affecting developers with enabled but unsecured local management endpoints.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.8.3CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Micronaut Framework versionCheck your project dependencies (build.gradle, pom.xml, or included JAR manifests) for the micronaut-version or micronaut-core library versionAffected if Version is below 3.8.3 (e.g., 3.8.0-3.8.2, or any 3.x version before 3.8.3)
-
Locate management endpoint configurationInspect your Micronaut configuration files (application.yml, application.yaml, or application.properties) for management endpoint settings such as endpoints, management, or micronaut.management entriesAffected if Management endpoints are explicitly enabled in configuration (e.g., endpoints.enabled: true or similar settings)
-
Verify if endpoints require authenticationReview your security configuration (security-enabled: true, intercept-url maps, or security rule settings) to confirm whether management endpoints have authentication requirementsAffected if Management endpoints are enabled but have no authentication or authorization rules applied (are publicly accessible)
-
Check for exposed localhost management portsInspect your runtime configuration for exposed management ports (typically 8081, 8090, or custom ports) that could receive cross-origin requests from browser contextsAffected if Management endpoints are bound to accessible ports and CORS is not restricting origins
You are affected if your Micronaut Framework version is below 3.8.3 AND you have management endpoints enabled without authentication or proper access controls.
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.
dbcve · scoped3.8.3
Upgrade Micronaut Framework to version 3.8.3 or later; additionally, disable unused management endpoints and secure any needed endpoints with proper authentication and access controls.
3.8.3
- 1. Identify the current Micronaut version in your project (check build.gradle, pom.xml, or gradle.properties)
- 2. Update the Micronaut dependency version to 3.8.3 or later in your build configuration
- 3. Rebuild your application to ensure dependencies resolve correctly
- 4. Run your test suite to verify the upgrade does not break existing functionality
- 5. If you use management/endpoints, verify they are properly secured (especially in production)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23639 — 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-23639 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