# CVE-2022-35120: Information disclosure in n/a

> An access control flaw in IXPdata EasyInstall allows attackers to read sensitive information stored in cleartext.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-r2rh-hpqm-rgj8

## What is CVE-2022-35120?

CVE-2022-35120 is a high-severity vulnerability in n/a, published on 1 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IXPdata EasyInstall 6.6.14725 contains an access control issue.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2022-35120?

It affects 1 product.


Products: Ixpdata Easyinstall.

## How do I fix CVE-2022-35120?

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

## Is CVE-2022-35120 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-35120 exists.

## Other vulnerabilities in n/a

- [CVE-2019-19897](https://insights.sbomify.com/CVE-2019-19897/): Command injection in n/a (critical 10.0)
- [CVE-2019-19896](https://insights.sbomify.com/CVE-2019-19896/): Misconfiguration in n/a (critical 9.9)
- [CVE-2023-30131](https://insights.sbomify.com/CVE-2023-30131/): Code injection in n/a (critical 9.8)
- [CVE-2019-19895](https://insights.sbomify.com/CVE-2019-19895/): Privilege escalation in n/a (high 8.8)
- [CVE-2023-27791](https://insights.sbomify.com/CVE-2023-27791/): Weak cryptography in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-35120 and fix it if it is affected.

What it is: CVE-2022-35120 is a high-severity vulnerability in n/a, published on 1 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-35120 exists.

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-2022-35120/ (Markdown: https://insights.sbomify.com/CVE-2022-35120/index.md)
```

## Sources

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

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