# CVE-2022-38491: Security feature bypass in n/a

> Attackers can bypass brute-force protections to compromise user accounts in EasyVista ITSM software.

- **Severity:** High 8.2 (`CVSS:3.1/AC:L/AV:N/A:N/C:H/I:L/PR:N/S:U/UI: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 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-6936-x6cq-f3xf

## What is CVE-2022-38491?

CVE-2022-38491 is a high-severity vulnerability in n/a, published on 10 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in EasyVista 2020.2.125.3 and 2022.1.109.0.03. Part of the application does not implement protection against brute-force attacks. Version 2022.1.133.0 corrects this issue.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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

It affects 1 product.


Products: Easyvista Service Manager.

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

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

## Is CVE-2022-38491 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-38490](https://insights.sbomify.com/CVE-2022-38490/): SQL injection in n/a (critical 9.6)
- [CVE-2022-38492](https://insights.sbomify.com/CVE-2022-38492/): SQL injection in n/a (high 7.7)
- [CVE-2021-33231](https://insights.sbomify.com/CVE-2021-33231/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2022-38489](https://insights.sbomify.com/CVE-2022-38489/): Cross-site scripting in n/a (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38491 is a high-severity vulnerability in n/a, published on 10 Jan 2023. 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-2022-38491 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-2022-38491/ (Markdown: https://insights.sbomify.com/CVE-2022-38491/index.md)
```

## Sources

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

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