Application Automation ToolsApplication · Microfocus
CVE-2021-22513
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMissing 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMissing authorization check in Micro Focus Application Automation Tools Jenkins plugin versions 6.7 and earlier allows attackers to bypass permission controls and access plugin functionality without proper authentication or authorization.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Application Automation ToolsApplication
<= 6.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Micro Focus Application Automation Tools plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or list installed plugins via Jenkins CLI: jenkins-cli.jar or REST API /pluginManager/api/json?tree=plugins[shortName,version]Affected if The plugin named 'Micro Focus Application Automation Tools' or similar variants appears in the installed plugins list
-
Identify the installed plugin versionIn the Jenkins web UI, find the Micro Focus Application Automation Tools plugin entry in the Installed plugins tab and note the Version column; alternatively, query the REST API endpoint /pluginManager/plugin/{plugin-name}/api/json for the version fieldAffected if The displayed version is 6.7 or any version lower than 6.7
-
Confirm the vulnerability appliesSince this is an authorization bypass affecting plugin functionality, the vulnerability applies if the plugin is installed and running on Jenkins with any version <= 6.7; no specific configuration toggle exists for this flawAffected if The plugin version is 6.7 or earlier (versions 6.0 through 6.7 inclusive, and any beta/alpha releases below 6.7)
If the Micro Focus Application Automation Tools Jenkins plugin is installed and its version is 6.7 or earlier, the environment is vulnerable to unauthorized access due to the missing authorization check.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade the Micro Focus Application Automation Tools plugin to a version newer than 6.7 that contains the authorization fix.
Fix this in Application Automation Tools
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22513 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-22513 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data