Check vulnerabilities

CVE exploitation data check using “IntheWild”

There are tens of thousands of vulnerabilities disclosed each year. Only a handful of them will ever be exploited.

Triaging vulnerabilities is hard, one thing is easy though: if you know something is actively exploited inTheWild you have to move within hours.

We believe that exploitation information is about safety and it should be easy to access and not be behind paywalls.

Get alerts on new reports of exploitation via RSS, Twitter, grab our docker image, the hourly database exports or get the full exploited list a /api/exploited

Most recently
exploited
in the wild

Vulnerability Feeds

CVE-2024-28253

Data reported first

04/18/2024

OpenMetadata is a unified platform for discovery, observability, and governance powered by a central metadata repository, in-depth lineage, and seamless team collaboration. `CompiledRule::validateExpression` is also called from `PolicyRepository.prepare`. `prepare()` is called from `EntityRepository.prepareInternal()` which, in turn, gets called from `EntityResource.createOrUpdate()`. Note that even though there is an authorization check (`authorizer.authorize()`), it gets called after `prepareInternal()` gets called and therefore after the SpEL expression has been evaluated. In order to reach this method, an attacker can send a PUT request to `/api/v1/policies` which gets handled by `PolicyResource.createOrUpdate()`. This vulnerability was discovered with the help of CodeQL's Expression language injection (Spring) query and is also tracked as `GHSL-2023-252`. This issue may lead to Remote Code Execution and has been addressed in version 1.3.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Reference

Credit

CVE-2024-28254

Data reported first

04/18/2024

OpenMetadata is a unified platform for discovery, observability, and governance powered by a central metadata repository, in-depth lineage, and seamless team collaboration. The `?AlertUtil::validateExpression` method evaluates an SpEL expression using `getValue` which by default uses the `StandardEvaluationContext`, allowing the expression to reach and interact with Java classes such as `java.lang.Runtime`, leading to Remote Code Execution. The `/api/v1/events/subscriptions/validation/condition/<expression>` endpoint passes user-controlled data `AlertUtil::validateExpession` allowing authenticated (non-admin) users to execute arbitrary system commands on the underlaying operating system. In addition, there is a missing authorization check since `Authorizer.authorize()` is never called in the affected path and, therefore, any authenticated non-admin user is able to trigger this endpoint and evaluate arbitrary SpEL expressions leading to arbitrary command execution. This vulnerability was discovered with the help of CodeQL's Expression language injection (Spring) query and is also tracked as `GHSL-2023-235`. This issue may lead to Remote Code Execution and has been addressed in version 1.2.4. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Reference

Credit

CVE-2024-28255

Data reported first

04/18/2024

OpenMetadata is a unified platform for discovery, observability, and governance powered by a central metadata repository, in-depth lineage, and seamless team collaboration. The `JwtFilter` handles the API authentication by requiring and verifying JWT tokens. When a new request comes in, the request's path is checked against this list. When the request's path contains any of the excluded endpoints the filter returns without validating the JWT. Unfortunately, an attacker may use Path Parameters to make any path contain any arbitrary strings. For example, a request to `GET /api/v1;v1%2fusers%2flogin/events/subscriptions/validation/condition/111` will match the excluded endpoint condition and therefore will be processed with no JWT validation allowing an attacker to bypass the authentication mechanism and reach any arbitrary endpoint, including the ones listed above that lead to arbitrary SpEL expression injection. This bypass will not work when the endpoint uses the `SecurityContext.getUserPrincipal()` since it will return `null` and will throw an NPE. This issue may lead to authentication bypass and has been addressed in version 1.2.4. Users are advised to upgrade. There are no known workarounds for this vulnerability. This issue is also tracked as `GHSL-2023-237`.

Reference

Credit

Thanks for the exploitation information!disclaimer

Know when
to panic

Get alerts for new exploited vulnerabilities

Be informed about the few vulnerabilities that really matter. Subscribe to the RSS and hook it up to your alerts channel, follow us on Twitter or look at our feed or API about new exploitations.

Prioritize vulnerabilities

Your vulnerability scanners probably return thousands of vulnerabilities. Triaging and prioritizing them is hard. Use our hourly database export or directly the our CLI to enrich your reports about exploits and exploitation activity.

Find Exploits

Need to verify a vulnerability or the exploit you found seems to be broken. We collect exploits from a number of different sources and do the github scouring for you. Check out the report page or automate your searches using the CLI.

Share exploitation information

If you identified a new exploitation activity during research or just saw some reports are missing from out database, you can Tweet @inthewildio or similarly tag us in you LinkedIn post. You can also just use this form.