# CVE-2023-37526: HCL DRYiCE Lucy v9 (now AEX) is affected by a Cross Origin Resource Sharing (CORS) Vulnerability

> A CORS misconfiguration in the HCL DRYiCE Lucy mobile app allows unauthorized access to resources from any domain and enables cache poisoning.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-prqw-x27x-86h2

## What is CVE-2023-37526?

CVE-2023-37526 is a medium-severity vulnerability in HCL Software DRYiCE Lucy, published on 10 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HCL DRYiCE Lucy (now AEX) is affected by a Cross Origin Resource Sharing (CORS) vulnerability. The mobile app is vulnerable to a CORS misconfiguration which could potentially allow unauthorized access to the application resources from any web domain and enable cache poisoning attacks.

Weakness: CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains)

## Which versions are affected by CVE-2023-37526?


## How do I fix CVE-2023-37526?

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

## Is CVE-2023-37526 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-37526 and fix it if it is affected.

What it is: CVE-2023-37526 is a medium-severity vulnerability in HCL Software DRYiCE Lucy, published on 10 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-37526 in the wild and no public exploit code.

Affected product: HCL Software DRYiCE Lucy. 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-2023-37526/ (Markdown: https://insights.sbomify.com/CVE-2023-37526/index.md)
```

## Sources

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

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