A melhor API para CVEs que encontrei até agora é no link . Por exemplo, se quisermos usar a API para obter informações sobre CVE-2016 -7395 , corremos
curl http://cve.circl.lu/api/cve/CVE-2016-7395
que retorna um JSON fornecido por
{
"Modified": "2016-09-11T06:59:26.727-04:00",
"Published": "2016-09-11T06:59:25.337-04:00",
"capec": [
{
"id": "230",
"name": "XML Nested Payloads",
"prerequisites": [
"An application uses an XML parser to perform transformation on user-controllable data.",
"An application does not perform sufficient validation to ensure that user-controllable data is safe for an XML parser."
],
"related_weakness": [
"112",
"20",
"19",
"674",
"770"
],
"solutions": [
"Carefully validate and sanitize all user-controllable data prior to passing it to the XML parser routine. Ensure that the resultant data is safe to pass to the XML parser.",
"Perform validation on canonical data.",
"Pick a robust implementation of an XML parser.",
"Validate XML against a valid schema or DTD prior to parsing."
],
"summary": [
"Applications often need to transform data in and out of the XML format by using an XML parser. It may be possible for an attacker to inject data that may have an adverse effect on the XML parser when it is being processed. By nesting XML data and causing this data to be continuously self-referential, an attacker can cause the XML parser to consume more resources while processing, causing excessive memory consumption and CPU utilization. An attacker's goal is to leverage parser failure to his or her advantage. In most cases this type of an attack will result in a denial of service due to an application becoming unstable, freezing, or crash. However it may be possible to cause a crash resulting in arbitrary code execution, leading to a jump from the data plane to the control plane [R.230.1]."
]
},
{
"id": "231",
"name": "XML Oversized Payloads",
"prerequisites": [
"An application uses an XML parser to perform transformation on user-controllable data.",
"An application does not perform sufficient validation to ensure that user-controllable data is safe for an XML parser."
],
"related_weakness": [
"112",
"20",
"19",
"674",
"770"
],
"solutions": [
"Carefully validate and sanitize all user-controllable data prior to passing it to the XML parser routine. Ensure that the resultant data is safe to pass to the XML parser.",
"Perform validation on canonical data.",
"Pick a robust implementation of an XML parser.",
"Validate XML against a valid schema or DTD prior to parsing."
],
"summary": [
"Applications often need to transform data in and out of the XML format by using an XML parser. It may be possible for an attacker to inject data that may have an adverse effect on the XML parser when it is being processed. By supplying oversized payloads in input vectors that will be processed by the XML parser, an attacker can cause the XML parser to consume more resources while processing, causing excessive memory consumption and CPU utilization, and potentially cause execution of arbitrary code. An attacker's goal is to leverage parser failure to his or her advantage. In many cases this type of an attack will result in a denial of service due to an application becoming unstable, freezing, or crash. However it is possible to cause a crash resulting in arbitrary code execution, leading to a jump from the data plane to the control plane [R.231.1]."
]
},
{
"id": "484",
"name": "XML Client-Side Attack",
"prerequisites": [
"An application uses an XML parser to perform transformation on user-controllable data.",
"An application does not perform sufficient validation to ensure that user-controllable data is safe for an XML parser."
],
"related_weakness": [
"112",
"20",
"19"
],
"solutions": [
"Carefully validate and sanitize all user-controllable data prior to passing it to the XML parser routine. Ensure that the resultant data is safe to pass to the XML parser.",
"The client software should have the latest patches and should be audited for vulnerabilities before being used to communicate with potentially hostile servers."
],
"summary": [
"Client applications such as web browsers that process HTML data often need to transform data in and out of the XML format by using an XML parser. It may be possible for an attacker to inject data that may have an adverse effect on the XML parser when it is being processed. These adverse effects may include the parser crashing, consuming too much of a resource, executing too slowly, executing code supplied by an attacker, allowing usage of unintended system functionality, etc. An attacker's goal is to leverage parser failure to his or her advantage. In some cases it may be possible to jump from the data plane to the control plane via bad data being passed to an XML parser. [R.484.1]"
]
},
{
"id": "99",
"name": "XML Parser Attack",
"prerequisites": [
"An application uses an XML parser to perform transformation on user-controllable data.",
"An application does not perform sufficient validation to ensure that user-controllable data is safe for an XML parser."
],
"related_weakness": [
"112",
"20",
"19",
"674",
"770"
],
"solutions": [
"Carefully validate and sanitize all user-controllable data prior to passing it to the XML parser routine. Ensure that the resultant data is safe to pass to the XML parser.",
"Perform validation on canonical data.",
"Pick a robust implementation of an XML parser.",
"Validate XML against a valid schema or DTD prior to parsing."
],
"summary": [
"Applications often need to transform data in and out of the XML format by using an XML parser. It may be possible for an attacker to inject data that may have an adverse effect on the XML parser when it is being processed. These adverse effects may include the parser crashing, consuming too much of a resource, executing too slowly, executing code supplied by an attacker, allowing usage of unintended system functionality, etc. An attacker's goal is to leverage parser failure to his or her advantage. In some cases it may be possible to jump from the data plane to the control plane via bad data being passed to an XML parser. [R.99.1]"
]
},
{
"id": "100",
"name": "Overflow Buffers",
"prerequisites": [
"Targeted software performs buffer operations.",
"Targeted software inadequately performs bounds-checking on buffer operations.",
"Attacker has the capability to influence the input to buffer operations."
],
"related_weakness": [
"120",
"119",
"131",
"129",
"805",
"19",
"680"
],
"solutions": [
"Use a language or compiler that performs automatic bounds checking.",
"Use secure functions not vulnerable to buffer overflow.",
"If you have to use dangerous functions, make sure that you do boundary checking.",
"Compiler-based canary mechanisms such as StackGuard, ProPolice and the Microsoft Visual Studio /GS flag. Unless this provides automatic bounds checking, it is not a complete solution.",
"Use OS-level preventative functionality. Not a complete solution.",
"Utilize static source code analysis tools to identify potential buffer overflow weaknesses in the software."
],
"summary": [
"Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an attacker. As a consequence, an attacker is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the attackers' choice."
]
}
],
"cvss": 6.8,
"cwe": "CWE-19",
"id": "CVE-2016-7395",
"last-modified": "2016-09-12T13:43:31.873-04:00",
"ranking": [
[
{
"circl": 2
}
]
],
"references": [
"https://codereview.chromium.org/2006143009",
"https://crbug.com/613918",
"https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html"
],
"summary": "SkPath.cpp in Skia, as used in Google Chrome before 53.0.2785.89 on Windows and OS X and before 53.0.2785.92 on Linux, does not properly validate the return values of ChopMonoAtY calls, which allows remote attackers to cause a denial of service (uninitialized memory access and application crash) or possibly have unspecified other impact via crafted graphics data.",
"vulnerable_configuration": [
{
"id": "cpe:2.3:a:google:chrome:52.0.2743.116",
"title": "Google Chrome 52.0.2743.116"
}
],
"vulnerable_configuration_cpe_2_2": [
"cpe:/a:google:chrome:52.0.2743.116"
]
}
Visite o link para obter mais informações sobre como usar a API.