Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
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. Impact 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.
Recommended action: Upgrade to 3.8.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
With a basic configuration like it is possible to access any file from a filesystem, using "/../../" in URL, as Micronaut does not restrict file access to configured paths. Repro Steps - create a file test.txt in /home/lstrmiska - start micronaut - execute command curl -v --path-as-is "http://localhost:8080/.assets/public/../test.txt" Impact Micronaut can potentially leak sensitive information. See https://cwe.mitre.org/data/definitions/22.html Patches Workarounds - do not use in mapping, use only which exposes only flat structure of a directory not allowing traversal - run micronaut in chroot (linux only) References See https://cwe.mitre.org/data/definitions/22.html For more information If you have any questions or comments about this advisory: Open an issue in Github Email us at info@micronaut.io
Recommended action: Upgrade to 2.5.9 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.