# CVE-2023-37511: HCL Traveler To Do is affected by App Transport Security (ATS) settings allowing insecure loads in web content

> Attackers can bypass App Transport Security to load insecure web content if specific ATS settings are configured incorrectly.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Aug 2023
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-hx3h-2x88-xvj3

## What is CVE-2023-37511?

CVE-2023-37511 is a low-severity vulnerability in HCL Traveler To Do, published on 11 Aug 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

If certain App Transport Security (ATS) settings are set in a certain manner, insecure loading of web content can be achieved.

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

It affects 1 product.


Products: Hcltech Traveler to Do.

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

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

## Is CVE-2023-37511 being exploited?

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

## Other vulnerabilities in HCL Traveler To Do

- [CVE-2023-37513](https://insights.sbomify.com/CVE-2023-37513/): HCL Traveler To Do is vulnerable to revealing sensitive information via the task switcher (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-37511 is a low-severity vulnerability in HCL Traveler To Do, published on 11 Aug 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-37511 in the wild and no public exploit code.

Affected product: HCL Traveler To Do. 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-37511/ (Markdown: https://insights.sbomify.com/CVE-2023-37511/index.md)
```

## Sources

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

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