# CVE-2019-14997: Information disclosure in Jira

> Remote attackers can obtain user details via caching flaws when Jira uses a reverse proxy or CDN, requiring configuration changes or upgrades.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Sep 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-3cvq-p878-rmp8

## What is CVE-2019-14997?

CVE-2019-14997 is a medium-severity vulnerability in Atlassian Jira Server, published on 11 Sep 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The AccessLogFilter class in Jira before version 8.4.0 allows remote anonymous attackers to learn details about other users, including their username, via an information expose through caching vulnerability when Jira is configured with a reverse Proxy and or a load balancer with caching or a CDN.

Weakness: CWE-524 (Use of Cache Containing Sensitive Information)

## Which versions are affected by CVE-2019-14997?

It affects 1 product.


Products: Atlassian Jira Server.

## How do I fix CVE-2019-14997?

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

## Is CVE-2019-14997 being exploited?

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

## Other vulnerabilities in Atlassian Jira Server

- [CVE-2019-11581](https://insights.sbomify.com/CVE-2019-11581/): Atlassian Jira Server and Data Center Server-Side Template Injection (critical 9.8, exploited in the wild)
- [CVE-2019-20400](https://insights.sbomify.com/CVE-2019-20400/): Code injection in Jira Server (high 7.8)
- [CVE-2020-14177](https://insights.sbomify.com/CVE-2020-14177/): Denial of service in Jira Server (medium 6.5)
- [CVE-2019-20401](https://insights.sbomify.com/CVE-2019-20401/): Cross-site request forgery in Jira Server (medium 6.5)
- [CVE-2019-14998](https://insights.sbomify.com/CVE-2019-14998/): Cross-site request forgery in Jira (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14997 and fix it if it is affected.

What it is: CVE-2019-14997 is a medium-severity vulnerability in Atlassian Jira Server, published on 11 Sep 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-14997 in the wild and no public exploit code.

Affected product: Atlassian Jira Server. 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-2019-14997/ (Markdown: https://insights.sbomify.com/CVE-2019-14997/index.md)
```

## Sources

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

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