CVE-2024-30730
Microsoft Un patches
Description
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that there was not reasonable evidence to determine the existence of a vulnerability.
INFO
Published Date :
April 10, 2024, 5:15 a.m.
Last Modified :
May 27, 2024, 1:15 a.m.
Source :
[email protected]
Remotely Exploitable :
No
Impact Score :
Exploitability Score :
Public PoC/Exploit Available at Github
CVE-2024-30730 has a 1 public PoC/Exploit
available at Github.
Go to the Public Exploits
tab to see the list.
Affected Products
The following products are affected by CVE-2024-30730
vulnerability.
Even if cvefeed.io
is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Insecure Logging Vulnerability in ROS Kinetic Kame
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-30730
vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-30730
vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 27, 2024
Action Type Old Value New Value Changed Description An insecure logging vulnerability has been identified within ROS Kinetic Kame in ROS_VERSION 1 and ROS_ PYTHON_VERSION 3, allows attackers to obtain sensitive information via inadequate security measures implemented within the logging mechanisms of ROS. NOTE: this is disputed by multiple third parties who believe there was not reasonable evidence to determine the existence of a vulnerability. Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that there was not reasonable evidence to determine the existence of a vulnerability. Removed Reference MITRE https://github.com/yashpatelphd/CVE-2024-30730 Removed Reference MITRE http://www.openwall.com/lists/oss-security/2024/04/23/4 Removed Reference MITRE http://www.openwall.com/lists/oss-security/2024/04/23/2 Removed Reference MITRE http://www.openwall.com/lists/oss-security/2024/04/23/3 Removed Reference MITRE http://www.openwall.com/lists/oss-security/2024/04/23/5 Removed Tag MITRE disputed -
CVE Rejected by [email protected]
May. 27, 2024
Action Type Old Value New Value -
CVE Translated by [email protected]
May. 27, 2024
Action Type Old Value New Value Removed Translation Title: ROS Kinetic Kame Description: Se ha identificado una vulnerabilidad de registro inseguro dentro de ROS Kinetic Kame en ROS_VERSION 1 y ROS_PYTHON_VERSION 3, que permite a los atacantes obtener información confidencial a través de medidas de seguridad inadecuadas implementadas dentro de los mecanismos de registro de ROS. -
CVE Modified by [email protected]
May. 17, 2024
Action Type Old Value New Value -
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
CVE Modified by [email protected]
May. 01, 2024
Action Type Old Value New Value Added Reference MITRE http://www.openwall.com/lists/oss-security/2024/04/23/5 [No types assigned] -
CVE Modified by [email protected]
May. 01, 2024
Action Type Old Value New Value Added Reference MITRE http://www.openwall.com/lists/oss-security/2024/04/23/3 [No types assigned] -
CVE Modified by [email protected]
May. 01, 2024
Action Type Old Value New Value Added Reference MITRE http://www.openwall.com/lists/oss-security/2024/04/23/4 [No types assigned] Added Reference MITRE http://www.openwall.com/lists/oss-security/2024/04/23/2 [No types assigned] -
CVE Modified by [email protected]
Apr. 17, 2024
Action Type Old Value New Value Changed Description An insecure logging vulnerability has been identified within ROS Kinetic Kame in ROS_VERSION 1 and ROS_ PYTHON_VERSION 3, allows attackers to obtain sensitive information via inadequate security measures implemented within the logging mechanisms of ROS. An insecure logging vulnerability has been identified within ROS Kinetic Kame in ROS_VERSION 1 and ROS_ PYTHON_VERSION 3, allows attackers to obtain sensitive information via inadequate security measures implemented within the logging mechanisms of ROS. NOTE: this is disputed by multiple third parties who believe there was not reasonable evidence to determine the existence of a vulnerability. Added Tag MITRE disputed -
CVE Received by [email protected]
Apr. 10, 2024
Action Type Old Value New Value Added Description An insecure logging vulnerability has been identified within ROS Kinetic Kame in ROS_VERSION 1 and ROS_ PYTHON_VERSION 3, allows attackers to obtain sensitive information via inadequate security measures implemented within the logging mechanisms of ROS. Added Reference MITRE https://github.com/yashpatelphd/CVE-2024-30730 [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-30730
is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-30730
weaknesses.