# CVE-2021-38283: Information disclosure in n/a

> Remote attackers can read sensitive application log files via a predictable URI in Wipro Holmes Orchestrator.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 29 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vrhq-hx93-3cxp

## What is CVE-2021-38283?

CVE-2021-38283 is a high-severity vulnerability in n/a, published on 29 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Wipro Holmes Orchestrator 20.4.1 (20.4.1_02_11_2020) allows remote attackers to read application log files containing sensitive information via a predictable /log URI.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2021-38283?

It affects 1 product.


Products: Wipro Holmes.

## How do I fix CVE-2021-38283?

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

## Is CVE-2021-38283 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-38147](https://insights.sbomify.com/CVE-2021-38147/): Missing authorization in n/a (high 7.5)
- [CVE-2021-38146](https://insights.sbomify.com/CVE-2021-38146/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-38283 and fix it if it is affected.

What it is: CVE-2021-38283 is a high-severity vulnerability in n/a, published on 29 Nov 2021. 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-2021-38283 in the wild and no public exploit code.

Affected product: n/a. 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-2021-38283/ (Markdown: https://insights.sbomify.com/CVE-2021-38283/index.md)
```

## Sources

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

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