# CVE-2021-22535: Information disclosure in Directory and Resource Administrator (DRA)

> An unauthorized information disclosure vulnerability in Micro Focus DRA allows attackers to access sensitive data without proper authorization.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-c4pp-f6g5-6wx8

## What is CVE-2021-22535?

CVE-2021-22535 is a medium-severity vulnerability in Directory and Resource Administrator (DRA), published on 28 Sep 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unauthorized information security disclosure vulnerability on Micro Focus Directory and Resource Administrator (DRA) product, affecting all DRA versions prior to 10.1 Patch 1. The vulnerability could lead to unauthorized information disclosure.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Microfocus Netiq Directory and Resource Administrator.

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

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

## Is CVE-2021-22535 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-22535 is a medium-severity vulnerability in Directory and Resource Administrator (DRA), published on 28 Sep 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-22535 in the wild and no public exploit code.

Affected product: Directory and Resource Administrator (DRA). 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-22535/ (Markdown: https://insights.sbomify.com/CVE-2021-22535/index.md)
```

## Sources

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

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