# CVE-2024-42169: HCL MyXalytics is affected by insecure direct object references

> Attackers can access or modify unauthorized data in HCL MyXalytics due to missing access control checks.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jan 2025
- **Updated:** 13 Jan 2025
- **Also known as:** GHSA-hfwr-76cx-qgg7

## What is CVE-2024-42169?

CVE-2024-42169 is a high-severity missing authorization vulnerability in HCL Software DRYiCE MyXalytics, published on 11 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2024-42169?

It affects 1 product.


Products: Hcltech Dryice Myxalytics.

## How do I fix CVE-2024-42169?

No fix has been published for CVE-2024-42169 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-42169 being exploited?

There is no known exploitation of CVE-2024-42169 in the wild and no public exploit code.

## Other vulnerabilities in HCL Software DRYiCE MyXalytics

- [CVE-2024-42168](https://insights.sbomify.com/CVE-2024-42168/): HCL MyXalytics is affected by out-of-band resource load (HTTP) vulnerability (high 8.9)
- [CVE-2023-45722](https://insights.sbomify.com/CVE-2023-45722/): Path Traversal Arbitrary File Read affects DRYiCE MyXalytics (high 8.8)
- [CVE-2023-50343](https://insights.sbomify.com/CVE-2023-50343/): Improper Access Control (Controller APIs) affects DRYiCE MyXalytics (high 8.3)
- [CVE-2023-45724](https://insights.sbomify.com/CVE-2023-45724/): Unauthenticated File Upload affects DRYiCE MyXalytics (high 8.2)
- [CVE-2023-50350](https://insights.sbomify.com/CVE-2023-50350/): A broken cryptographic algorithm impacts MyXalytics (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-42169 and fix it if it is affected.

What it is: CVE-2024-42169 is a high-severity missing authorization vulnerability in HCL Software DRYiCE MyXalytics, published on 11 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-42169 in the wild and no public exploit code.

Affected product: HCL Software DRYiCE MyXalytics. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-42169/ (Markdown: https://insights.sbomify.com/CVE-2024-42169/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-42169
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-42169
- OSV: https://osv.dev/vulnerability/CVE-2024-42169

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-42169/
Summaries are generated and may contain mistakes; the official description above is the record.