Show filters
432 Total Results
Displaying 81-90 of 432
Sort by:
Attacker Value
Unknown
CVE-2022-22373
Disclosure Date: June 30, 2022 (last updated October 07, 2023)
An improper validation vulnerability in IBM InfoSphere Information Server 11.7 Pack for SAP Apps and BW Packs may lead to creation of directories and files on the server file system that may contain non-sensitive debugging information like stack traces. IBM X-Force ID: 221323.
0
Attacker Value
Unknown
CVE-2022-31768
Disclosure Date: June 05, 2022 (last updated October 07, 2023)
IBM InfoSphere Information Server 11.7 is vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the attacker to view, add, modify or delete information in the back-end database.
0
Attacker Value
Unknown
CVE-2022-22454
Disclosure Date: May 09, 2022 (last updated October 07, 2023)
IBM InfoSphere Information Server 11.7 could allow a locally authenticated attacker to execute arbitrary commands on the system by sending a specially crafted request.
0
Attacker Value
Unknown
CVE-2022-22427
Disclosure Date: April 27, 2022 (last updated October 07, 2023)
IBM InfoSphere Information Server 11.7 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 223720.
0
Attacker Value
Unknown
CVE-2022-22322
Disclosure Date: April 27, 2022 (last updated October 07, 2023)
IBM InfoSphere Information Server 11.7 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 218370.
0
Attacker Value
Unknown
CVE-2021-38952
Disclosure Date: April 27, 2022 (last updated October 07, 2023)
IBM InfoSphere Information Server 11.7 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 211408.
0
Attacker Value
Unknown
CVE-2022-22443
Disclosure Date: April 27, 2022 (last updated October 07, 2023)
IBM InfoSphere Information Server 11.7 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 224440.
0
Attacker Value
Unknown
CVE-2022-22441
Disclosure Date: April 27, 2022 (last updated October 07, 2023)
IBM InfoSphere Information Server 11.7 could allow an authenticated user to view information of higher privileged users and groups due to a privilege escalation vulnerability. IBM X-Force ID: 224426.
0
Attacker Value
Unknown
CVE-2022-23437
Disclosure Date: January 24, 2022 (last updated November 28, 2024)
There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads. This causes, the XercesJ XML parser to wait in an infinite loop, which may sometimes consume system resources for prolonged duration. This vulnerability is present within XercesJ version 2.12.1 and the previous versions.
0
Attacker Value
Unknown
CVE-2022-23305
Disclosure Date: January 18, 2022 (last updated October 07, 2023)
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
0