# CVE-2021-22513: Missing permission checks in Micro Focus Application Automation Tools Plugin

> Attackers can access protected resources without permission checks in the Micro Focus Application Automation Tools Jenkins plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Apr 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-7qp2-rgxr-29q4

## What is CVE-2021-22513?

CVE-2021-22513 is a medium-severity missing authorization vulnerability in Micro Focus Application Automation Tools Plugin - Jenkins plugin., published on 8 Apr 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Missing Authorization vulnerability in Micro Focus Application Automation Tools Plugin - Jenkins plugin. The vulnerability affects version 6.7 and earlier versions. The vulnerability could allow access without permission checks.

Weakness: CWE-862 (Missing Authorization)

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

2 open source packages ship an affected version, including org.jenkins-ci.plugins:hp-application-automation-tools-plugin. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:hp-application-automation-tools-plugin` | Maven | All versions | 7.2.3-beta |
| `org.jenkins-ci.plugins:hp-application-automation-tools-plugin` | Maven | All versions | 7.2.3-beta |

Products: Microfocus Application Automation Tools.

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

Upgrade org.jenkins-ci.plugins:hp-application-automation-tools-plugin to 7.2.3-beta or later.

## Is CVE-2021-22513 being exploited?

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

## Other vulnerabilities in Micro Focus Application Automation Tools Plugin - Jenkins plugin.

- [CVE-2021-22511](https://insights.sbomify.com/CVE-2021-22511/): SSL/TLS certificate validation unconditionally disabled by Jenkins Micro Focus Application Automation Tools Plugin (medium 6.5)
- [CVE-2021-22512](https://insights.sbomify.com/CVE-2021-22512/): CSRF vulnerability in Jenkins Micro Focus Application Automation Tools Plugin (medium 6.5)
- [CVE-2021-22510](https://insights.sbomify.com/CVE-2021-22510/): Reflected XSS vulnerability in Jenkins Micro Focus Application Automation Tools Plugin (medium 6.1)
- [CVE-2024-4184](https://insights.sbomify.com/CVE-2024-4184/): Multiple XXE sinks in ALM archive post-build step in OpenText Application Automation Tools (medium 5.9)
- [CVE-2024-4189](https://insights.sbomify.com/CVE-2024-4189/): Multiple XXE sinks in Run LoadRunner script step in OpenText Application Automation Tools (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-22513 is a medium-severity missing authorization vulnerability in Micro Focus Application Automation Tools Plugin - Jenkins plugin., published on 8 Apr 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-22513 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:hp-application-automation-tools-plugin (Maven): affected all versions; fixed in 7.2.3-beta
- org.jenkins-ci.plugins:hp-application-automation-tools-plugin (Maven): affected all versions; fixed in 7.2.3-beta

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

## Sources

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

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