9 matches found
EUVD-2024-54770
Malicious code in bioql PyPI...
CVE-2024-38327
IBM Analytics Content Hub 2.0, 2.1, 2.2, and 2.3 is vulnerable to information exposure and further attacks due to an exposed JavaScript source map which could assist an attacker to read and debug JavaScript used in the application's API...
CVE-2024-38327
IBM Analytics Content Hub 2.0, 2.1, 2.2, and 2.3 is vulnerable to information exposure and further attacks due to an exposed JavaScript source map which could assist an attacker to read and debug JavaScript used in the application's API...
CVE-2024-38327
IBM Analytics Content Hub 2.0, 2.1, 2.2, and 2.3 is vulnerable to information exposure and further attacks due to an exposed JavaScript source map which could assist an attacker to read and debug JavaScript used in the application's API...
CVE-2024-38327
CVE-2024-38327 affects IBM Analytics Content Hub (versions 2.0–2.3). Affected component is the exposed JavaScript source map, which can enable information disclosure and potentially aid attacks by reading/debugging the API’s JavaScript. The reported impact is information exposure with potential f...
CVE-2024-38327 IBM Analytics Content Hub information disclosure
IBM Analytics Content Hub 2.0, 2.1, 2.2, and 2.3 is vulnerable to information exposure and further attacks due to an exposed JavaScript source map which could assist an attacker to read and debug JavaScript used in the application's API...
CVE-2024-38327 IBM Analytics Content Hub information disclosure
IBM Analytics Content Hub 2.0, 2.1, 2.2, and 2.3 is vulnerable to information exposure and further attacks due to an exposed JavaScript source map which could assist an attacker to read and debug JavaScript used in the application's API...
PT-2025-29095 · Ibm · Ibm Analytics Content Hub
Name of the Vulnerable Software and Affected Versions: IBM Analytics Content Hub versions 2.0 through 2.3 Description: IBM Analytics Content Hub is susceptible to information disclosure and potential further attacks due to an exposed JavaScript source map. This exposure could allow an attacker to...
Trint Ltd: Insecure Zendesk SSO implementation by generating JWT client-side
Summary: app.trint.com implements SSO to Zendesk, it does this by using JWT as described at https://support.zendesk.com/hc/en-us/articles/203663816-Enabling-JWT-JSON-Web-Token-single-sign-on This functionality has not been implemented securely because the JWT generation happens in the client-side...