823 matches found
CVE-2019-4337
IBM Robotic Process Automation with Automation Anywhere 11 could allow an attacker to obtain sensitive information due to missing authentication in Ignite nodes. IBM X-Force ID: 161412...
Authentication flaw
IBM Robotic Process Automation with Automation Anywhere 11 could allow an attacker to obtain sensitive information due to missing authentication in Ignite nodes. IBM X-Force ID: 161412...
CVE-2019-4337
IBM Robotic Process Automation with Automation Anywhere 11 could allow an attacker to obtain sensitive information due to missing authentication in Ignite nodes. IBM X-Force ID: 161412...
CVE-2019-4337
CVE-2019-4337 affects IBM Robotic Process Automation with Automation Anywhere (version 11). The IBM bulletin documents an information-disclosure vulnerability caused by missing authentication in Ignite cluster nodes, enabling an attacker to obtain sensitive information. CVSS details in the entry ...
PT-2019-17039 · Automation Anywhere +1 · Automation Anywhere +1
Name of the Vulnerable Software and Affected Versions: IBM Robotic Process Automation with Automation Anywhere version 11 Description: The issue is related to missing authentication in Ignite nodes, which could allow an attacker to obtain sensitive information. Recommendations: For IBM Robotic...
CVE-2019-4337: Missing Authentication for Critical Function
IBM Robotic Process Automation with Automation Anywhere 11 could allow an attacker to obtain sensitive information due to missing authentication in Ignite nodes. IBM X-Force ID: 161412...
Security Bulletin: IBM Robotic Process Automation Ignite Cluster Nodes are missing authentication (CVE-2019-4337)
Summary IBM Robotic Process Automation Ignite Cluster Nodes are missing authentication Vulnerability Details CVEID: CVE-2019-4337 DESCRIPTION: IBM Robotic Process Automation with Automation Anywhere could allow an attacker to obtain sensitive information due to missing authentication in Ignite...
GHSA-2R5H-GH4X-8HP9 Resources Downloaded over Insecure Protocol in igniteui
Affected versions of igniteui download Javascript and CSS resources over an unencrypted HTTP connection. An attacker with a privileged network position can intercept and view or modify any content sent or recieved over an unencrypted HTTP connection. Recommendation The igniteui package has been...
Resources Downloaded over Insecure Protocol in igniteui
Affected versions of igniteui download Javascript and CSS resources over an unencrypted HTTP connection. An attacker with a privileged network position can intercept and view or modify any content sent or recieved over an unencrypted HTTP connection. Recommendation The igniteui package has been...
ignite: Improper deserialization allows for code execution via GridClientJdkMarshaller endpoint
In Apache Ignite before 2.4.8 and 2.5.x before 2.5.3, the serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be...
Moderate severity vulnerability that affects com.sparkjava:spark-core
In Spark before 2.7.2, a remote attacker can read unintended static files via various representations of absolute or relative pathnames, as demonstrated by file: URLs and directory traversal sequences. NOTE: this product is unrelated to Ignite Realtime Spark...
com.srotya.tau:tau-alerts (>=0.0.5, <=0.0.8), com.srotya.tau:tau-dengine (>=0.0.5, <=0.0.8) +37 more potentially affected by CVE-2018-8018 via org.apache.ignite:ignite-core (1.4.0)
org.apache.ignite:ignite-core MAVEN version 1.4.0 is affected by a known vulnerability. The following packages have a transitive dependency on org.apache.ignite:ignite-core and may be impacted: - com.srotya.tau:tau-alerts =0.0.5, =0.0.5, =0.0.5, =0.0.5, =0.16.0-rc1, =0.0.18, =0.0.18, =0.0.18,...
com.ecfront:ezf-message (>=3.0.0-beta1, <=3.0.0-beta3), com.jiuxian:mossrose (>=1.1.0-release, <=1.3.2-release) +46 more potentially affected by CVE-2018-8018 via org.apache.ignite:ignite-core (1.5.0.final)
org.apache.ignite:ignite-core MAVEN version 1.5.0.final is affected by a known vulnerability. The following packages have a transitive dependency on org.apache.ignite:ignite-core and may be impacted: - com.ecfront:ezf-message =3.0.0-beta1, =1.1.0-release, =1.0.0-release, =0.0.5, =0.18.0-rc1,...
com.github.itzmedinesh:micro-cache-grid (1.0.0), com.github.pires:apache-ignite-discovery-kubernetes (>=1.0, <=1.0_1) +52 more potentially affected by CVE-2018-8018 via org.apache.ignite:ignite-core (1.6.0)
org.apache.ignite:ignite-core MAVEN version 1.6.0 is affected by a known vulnerability. The following packages have a transitive dependency on org.apache.ignite:ignite-core and may be impacted: - com.github.itzmedinesh:micro-cache-grid 1.0.0 - com.github.pires:apache-ignite-discovery-kubernetes...
com.github.dexecutor:dexecutor-ignite (>=0.0.1, <=1.0.1), com.jiuxian:mossrose (>=1.3.3-release, <=1.4.1-release) +47 more potentially affected by CVE-2018-8018 via org.apache.ignite:ignite-core (1.7.0)
org.apache.ignite:ignite-core MAVEN version 1.7.0 is affected by a known vulnerability. The following packages have a transitive dependency on org.apache.ignite:ignite-core and may be impacted: - com.github.dexecutor:dexecutor-ignite =0.0.1, =1.3.3-release, =1.0.0-release, =1.1.2-release,...
com.ecfront.dew:cluster-spi-ignite (>=1.0.0, <=1.1.4), com.fnklabs.draenei:ignite (0.8.5) +47 more potentially affected by CVE-2018-8018 via org.apache.ignite:ignite-core (1.9.0)
org.apache.ignite:ignite-core MAVEN version 1.9.0 is affected by a known vulnerability. The following packages have a transitive dependency on org.apache.ignite:ignite-core and may be impacted: - com.ecfront.dew:cluster-spi-ignite =1.0.0, =2.0.7-release, =3.4.0, =3.4.0, =2.19.0, =2.19.0, =2.19.5 ...
GHSA-QCJV-WFCG-MMPR Code execution via deserialization in org.apache.ignite:ignite-core
Apache Ignite 2.5 and earlier serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one sends a...
Code execution via deserialization in org.apache.ignite:ignite-core
Apache Ignite 2.5 and earlier serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one sends a...
Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization
In Apache Ignite 2.3 or earlier, the serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one...
GHSA-CHP4-RV79-68J3 Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization
In Apache Ignite 2.3 or earlier, the serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one...