CVE-2024-36360

Description

OS command injection vulnerability exists in awkblog v0.0.1 (commit hash:7b761b192d0e0dc3eef0f30630e00ece01c8d552) and earlier. If a remote unauthenticated attacker sends a specially crafted HTTP request, an arbitrary OS command may be executed with the privileges of the affected product on the machine running the product.

Category

9.8
CVSS
Severity: Critical
CVSS 3.1 •
EPSS 1.96% Top 20%
Affected: Keisuke Nakayama awkblog
Published at:
Updated at:

References

Link Tags
https://github.com/yammerjp/awkblog/issues/1
https://jvn.jp/en/jp/JVN80506242/

Frequently Asked Questions

What is the severity of CVE-2024-36360?
CVE-2024-36360 has been scored as a critical severity vulnerability.
How to fix CVE-2024-36360?
To fix CVE-2024-36360, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2024-36360 being actively exploited in the wild?
It is possible that CVE-2024-36360 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~2% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2024-36360?
CVE-2024-36360 affects Keisuke Nakayama awkblog.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.