| CVE-2024-22349 | FAIBLE3.3 | IBM DevOps Velocity 5.0.0 and IBM UrbanCode Velocity 4.0.0 through 4.0. 25 allows web pages to be stored locally which can be read by another user on the system. | 20/01/2025 |
| CVE-2024-22348 | ÉLEVÉE7.5 | IBM DevOps Velocity 5.0.0 and IBM UrbanCode Velocity 4.0.0 through 4.0. 25 uses Cross-Origin Resource Sharing (CORS) which could allow an attacker to carry out privileged actions and retrieve sensitive information as the domain name is not being limited to only trusted domains. | 20/01/2025 |
| CVE-2024-22347 | ÉLEVÉE7.5 | IBM DevOps Velocity 5.0.0 and IBM UrbanCode Velocity 4.0.0 through 4.0. 25 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. | 20/01/2025 |
| CVE-2024-42181 | ÉLEVÉE7.5 | HCL MyXalytics is affected by a cleartext transmission of sensitive information vulnerability. The application transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors. | 12/01/2025 |
| CVE-2024-42180 | CRITIQUE9.8 | HCL MyXalytics is affected by a malicious file upload vulnerability. The application accepts invalid file uploads, including incorrect content types, double extensions, null bytes, and special characters, allowing attackers to upload and execute malicious files. | 12/01/2025 |
| CVE-2024-42179 | FAIBLE2.7 | HCL MyXalytics is affected by sensitive information disclosure vulnerability. The HTTP response header exposes the Microsoft-HTTP API∕2.0 as the server's name & version. | 12/01/2025 |
| CVE-2024-42175 | CRITIQUE9.8 | HCL MyXalytics is affected by a weak input validation vulnerability. The application accepts special characters and there is no length validation. This can lead to security vulnerabilities like SQL injection, XSS, and buffer overflow. | 11/01/2025 |
| CVE-2024-42174 | FAIBLE3.7 | HCL MyXalytics is affected by username enumeration vulnerability. This allows a malicious user to perform enumeration of application users, and therefore compile a list of valid usernames. | 11/01/2025 |
| CVE-2024-42173 | MOYENNE4.8 | HCL MyXalytics is affected by an improper password policy implementation vulnerability. Weak passwords and lack of account lockout policies allow attackers to guess or brute-force passwords if the username is known. | 11/01/2025 |
| CVE-2024-42172 | CRITIQUE9.8 | HCL MyXalytics is affected by broken authentication. It allows attackers to compromise keys, passwords, and session tokens, potentially leading to identity theft and system control. This vulnerability arises from poor configuration, logic errors, or software bugs and can affect any application with access control, in | 11/01/2025 |
| CVE-2024-42171 | MOYENNE6.4 | HCL MyXalytics is affected by a session fixation vulnerability. Cyber-criminals can exploit this by sending crafted URLs with a session token to access the victim's login session. | 11/01/2025 |
| CVE-2024-42170 | MOYENNE6.8 | HCL MyXalytics is affected by a session fixation vulnerability. Cyber-criminals can exploit this by sending crafted URLs with a session token to access the victim's login session. | 11/01/2025 |
| CVE-2024-42169 | ÉLEVÉE8.1 | HCL MyXalytics is affected by insecure direct object references. It occurs due to missing access control checks, which fail to verify whether a user should be allowed to access specific data. | 11/01/2025 |
| CVE-2024-42168 | CRITIQUE9.4 | HCL MyXalytics is affected by out-of-band resource load (HTTP) vulnerability. An attacker can deploy a web server that returns malicious content, and then induce the application to retrieve and process that content. | 11/01/2025 |
| CVE-2024-42188 | MOYENNE4.6 | HCL Connections is vulnerable to a broken access control vulnerability that may allow an unauthorized user to update data in certain scenarios. | 14/11/2024 |
| CVE-2024-30133 | MOYENNE5.3 | HCL Traveler for Microsoft Outlook (HTMO) is susceptible to a control flow vulnerability. The application does not sufficiently manage its control flow during execution, creating conditions in which the control flow can be modified in unexpected ways. | 12/11/2024 |
| CVE-2024-30142 | FAIBLE3.8 | HCL BigFix Compliance is affected by a missing secure flag on a cookie. If a secure flag is not set, cookies may be stolen by an attacker using XSS, resulting in unauthorized access or session cookies could be transferred over an unencrypted channel. | 07/11/2024 |
| CVE-2024-30141 | MOYENNE4.7 | HCL BigFix Compliance is vulnerable to the generation of error messages containing sensitive information. Detailed error messages can provide enticement information or expose information about its environment, users, or associated data. | 07/11/2024 |
| CVE-2024-30140 | MOYENNE5.4 | HCL BigFix Compliance is affected by unvalidated redirects and forwards. The HOST header can be manipulated by an attacker and as a result, it can poison the web cache and provide back to users being served the page. | 07/11/2024 |
| CVE-2024-30149 | MOYENNE6.5 | HCL AppScan Source <= 10.6.0 does not properly validate a TLS/SSL certificate for an executable. | 31/10/2024 |