4415 matches found
CVE-2020-5002 IBM Financial Transaction Manager security bypass
IBM Financial Transaction Manager 3.2.0 through 3.2.10 could allow an authenticated user to perform unauthorized actions due to improper validation. IBM X-Force ID: 192954...
CVE-2020-5002 IBM Financial Transaction Manager security bypass
IBM Financial Transaction Manager 3.2.0 through 3.2.10 could allow an authenticated user to perform unauthorized actions due to improper validation. IBM X-Force ID: 192954...
CVE-2020-5002
IBM Financial Transaction Manager (for Corporate, Digital, and High Value Payments) versions 3.2.0–3.2.10 are affected by CVE-2020-5002 due to improper validation, potentially allowing an authenticated user to perform unauthorized actions. The IBM security bulletin specifies the affected product ...
CVE-2020-5001 IBM Financial Transaction Manager path traversal
IBM Financial Transaction Manager 3.2.0 through 3.2.7 could allow a remote attacker to traverse directories on the system. An attacker could send a specially-crafted URL request containing "dot dot" sequences /../ to view arbitrary files on the system. IBM X-Force ID: 192953...
CVE-2020-5001
IBM Financial Transaction Manager versions 3.2.0–3.2.7 are affected by a directory traversal vulnerability that allows a remote attacker to view arbitrary files by sending URL requests containing dot dot sequences (/../). The issue is described across multiple sources as a path traversal flaw wit...
CVE-2020-5001 IBM Financial Transaction Manager path traversal
IBM Financial Transaction Manager 3.2.0 through 3.2.7 could allow a remote attacker to traverse directories on the system. An attacker could send a specially-crafted URL request containing "dot dot" sequences /../ to view arbitrary files on the system. IBM X-Force ID: 192953...
PT-2023-11912 · Ibm · Ibm Financial Transaction Manager
Name of the Vulnerable Software and Affected Versions: IBM Financial Transaction Manager versions 3.2.0 through 3.2.7 Description: The issue allows a remote attacker to traverse directories on the system by sending a specially-crafted URL request containing "dot dot" sequences /../ to view...
IBM Financial Transaction Manager 路径遍历漏洞
IBM Financial Transaction Manager is a financial transaction manager from International Business Machines IBM, Inc. A directory traversal security vulnerability exists in IBM Financial Transaction Manager, which could be exploited by a remote attacker to submit a special request in the applicatio...
IBM Financial Transaction Manager 安全漏洞
IBM Financial Transaction Manager is a financial transaction manager from International Business Machines IBM. The product is primarily used for monitoring, tracking and reporting financial payments and transactions. A security vulnerability exists in IBM Financial Transaction Manager versions...
PT-2023-11914 · Ibm · Ibm Financial Transaction Manager For Digital Payments
Name of the Vulnerable Software and Affected Versions: IBM Financial Transaction Manager for Digital Payments for Multi-Platform versions 3.2.0 through 3.2.7 Description: The issue allows a remote attacker to obtain sensitive information when a detailed technical error message is returned in the...
AZL-13822 CVE-2023-1095 affecting package kernel for versions less than 5.15.102.1-1
In nftablesupdtable, if nftablestableenable returns an error, nfttransdestroy is called to free the transaction object. nfttransdestroy calls listdel, but the transaction was never placed on a list -- the list head is all zeroes, this results in a NULL pointer dereference...
CVE-2023-1095
In nftablesupdtable, if nftablestableenable returns an error, nfttransdestroy is called to free the transaction object. nfttransdestroy calls listdel, but the transaction was never placed on a list -- the list head is all zeroes, this results in a NULL pointer dereference...
DEBIAN-CVE-2023-1095
In nftablesupdtable, if nftablestableenable returns an error, nfttransdestroy is called to free the transaction object. nfttransdestroy calls listdel, but the transaction was never placed on a list -- the list head is all zeroes, this results in a NULL pointer dereference...
UBUNTU-CVE-2023-1095
In nftablesupdtable, if nftablestableenable returns an error, nfttransdestroy is called to free the transaction object. nfttransdestroy calls listdel, but the transaction was never placed on a list -- the list head is all zeroes, this results in a NULL pointer dereference...
CVE-2023-1095
In nftablesupdtable, if nftablestableenable returns an error, nfttransdestroy is called to free the transaction object. nfttransdestroy calls listdel, but the transaction was never placed on a list -- the list head is all zeroes, this results in a NULL pointer dereference...
CVE-2023-20938
In bindertransactionbufferrelease of binder.c, there is a possible use after free due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android...
DEBIAN-CVE-2023-20938
In bindertransactionbufferrelease of binder.c, there is a possible use after free due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android...
UBUNTU-CVE-2023-20938
In bindertransactionbufferrelease of binder.c, there is a possible use after free due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android...
CVE-2023-1095
In nftablesupdtable, if nftablestableenable returns an error, nfttransdestroy is called to free the transaction object. nfttransdestroy calls listdel, but the transaction was never placed on a list -- the list head is all zeroes, this results in a NULL pointer dereference...
CVE-2023-1095
In nftablesupdtable, if nftablestableenable returns an error, nfttransdestroy is called to free the transaction object. nfttransdestroy calls listdel, but the transaction was never placed on a list -- the list head is all zeroes, this results in a NULL pointer dereference...