{"answers":{"affected":"2 open source packages ship an affected version, including io.micronaut:micronaut-http. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-21700 in the wild and no public exploit code.","fix":"Upgrade io.micronaut:micronaut-http to 3.2.7 or later.","what":"CVE-2022-21700 is a medium-severity denial of service vulnerability in micronaut-projects micronaut-core, published on 18 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-21700 and fix it if it is affected.\n\nWhat it is: CVE-2022-21700 is a medium-severity denial of service vulnerability in micronaut-projects micronaut-core, published on 18 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-21700 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.micronaut:micronaut-http (Maven): affected all versions; fixed in 3.2.7\n- io.micronaut:micronaut-http (Maven): affected all versions; fixed in 3.2.7\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-21700/ (Markdown: https://insights.sbomify.com/CVE-2022-21700/index.md)","id":"CVE-2022-21700","markdown":"https://insights.sbomify.com/CVE-2022-21700/index.md","name":"CVE-2022-21700","record":{"aliases":["GHSA-2457-2263-mm9f"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Java web framework","requires_auth":"none","summary":"Attackers can cause a memory leak and potential denial of service by sending invalid Content Type headers to applications using the Micronaut framework.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"micronaut","vendor":"objectcomputing"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Micronaut is a JVM-based, full stack Java framework designed for building JVM web applications with support for Java, Kotlin and the Groovy language. In affected versions sending an invalid Content Type header leads to memory leak in DefaultArgumentConversionContext as this type is erroneously used in static state. ### Impact Sending an invalid Content Type header leads to memory leak in `DefaultArgumentConversionContext` as this type is erroneously used in static state. ### Patches The problem is patched in Micronaut 3.2.7 and above. ### Workarounds The default content type binder can be replaced in an existing Micronaut application to mitigate the issue: ```java package example; import java.util.List; import io.micronaut.context.annotation.Replaces; import io.micronaut.core.convert.ConversionService; import io.micronaut.http.MediaType; import io.micronaut.http.bind.DefaultRequestBinderRegistry; import io.micronaut.http.bind.binders.RequestArgumentBinder; import jakarta.inject.Singleton; @Singleton @Replaces(DefaultRequestBinderRegistry.class) class FixedRequestBinderRegistry extends DefaultRequestBinderRegistry { public FixedRequestBinderRegistry(ConversionService conversionService, List\u003cRequestArgumentBinder\u003e binders) { super(conversionService, binders); } @Override protected void registerDefaultConverters(ConversionService\u003c?\u003e conversionService) { super.registerDefaultConverters(conversionService); conversionService.addConverter(CharSequence.class, MediaType.class, charSequence -\u003e { try { return MediaType.of(charSequence); } catch (IllegalArgumentException e) { return null; } }); } } ``` ### References Commit that introduced the vulnerability https://github.com/micronaut-projects/micronaut-core/commit/b8ec32c311689667c69ae7d9f9c3b3a8abc96fe3 ### For more information If you have any questions or comments about this advisory: * Open an issue in [Micronaut Core](https://github.com/micronaut-projects/micronaut-core/issues) * Email us at [info@micronaut.io](mailto:info@micronaut.io)","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Memory leak in micronaut-core","id":"CVE-2022-21700","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"denial_of_service","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Privileged Escalation in Istio","id":"CVE-2022-21701"},"packages":[{"ecosystem":"Maven","fixed":["3.2.7"],"introduced":["0"],"last_affected":[],"package":"io.micronaut:micronaut-http","purl":null,"source":"GHSA-2457-2263-mm9f"},{"ecosystem":"Maven","fixed":["3.2.7"],"introduced":["0"],"last_affected":[],"package":"io.micronaut:micronaut-http","purl":"pkg:maven/io.micronaut/micronaut-http","source":"GHSA-2457-2263-mm9f"}],"prev":{"headline":"Execution with Unnecessary Privileges in ipython","id":"CVE-2022-21699"},"products":["micronaut-core"],"published":"2022-01-18","related":[{"cvss_score":9.8,"headline":"Micronaut's HTTP client is vulnerable to HTTP Request Header Injection","id":"CVE-2020-7611","kev_date_added":null,"published":"2020-03-30"},{"cvss_score":8.2,"headline":"Micronaut vulnerable to DoS via crafted form-urlencoded body binding with descending array indices","id":"CVE-2026-33013","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.5,"headline":"Micronaut Framework vulnerable to a Denial of Service in HTML error response caching","id":"CVE-2026-33012","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.5,"headline":"Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in micronaut-core","id":"CVE-2021-32769","kev_date_added":null,"published":"2021-07-16"},{"cvss_score":5.1,"headline":"micronaut-core management endpoints vulnerable to drive-by localhost attack","id":"CVE-2024-23639","kev_date_added":null,"published":"2024-02-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["micronaut-projects"]},"summary":"Attackers can cause a memory leak and potential denial of service by sending invalid Content Type headers to applications using the Micronaut framework.","url":"https://insights.sbomify.com/CVE-2022-21700/"}