CVE-2019-20405Network attack vector

JMX monitoring changes via cross-site request forgery

Published Feb 6, 2020 · Updated Sep 16, 2024

Cross-site request forgery in Atlassian Jira Server before 8.6.0 allows remote attackers to toggle the JMX monitoring flag. Atlassian identifies the affected locus only as the JMX monitoring flag and has not published the request handler or the omitted anti-CSRF validation. A user with an active session and access to the setting must follow a crafted request, after which monitoring can be enabled or disabled without that user's intent.

CVSS severity4.3
Medium
EPSS probability0.55%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Cross-site request forgery in Atlassian Jira Server before 8.6.0 allows remote attackers to toggle the JMX monitoring flag. Atlassian identifies the affected locus only as the JMX monitoring flag and has not published the request handler or the omitted anti-CSRF validation. A user with an active session and access to the setting must follow a crafted request, after which monitoring can be enabled or disabled without that user's intent.

The record

CVE
CVE-2019-20405
Published
Feb 6, 2020
Updated
Sep 16, 2024
Vendor
Atlassian
Product
Jira Server
Classifications
CWE-352
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Feb 6, 2020CVE publishedPublication date reported by the CVE source.
  2. Sep 16, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=unspecified <8.6.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Atlassian · Jira Serverversion=unspecified <8.6.0

Published CVSS scores

4.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
4.3NIST NVDAV:N/AC:M/Au:N/C:N/I:P/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-352Cross-Site Request Forgery (CSRF)

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo