HIGH CVSS 8.8
Published: 2025-05-20

CVE-2025-22157

atlassian jira_data_center Security Advisory (CVE-2025-22157)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2025-22157?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2025-22157 impacting atlassian jira_data_center. Evaluated with CVSS Base Score of 8.8 (HIGH).

Original NVD Description

Source: NIST NVD
This High severity PrivEsc (Privilege Escalation) vulnerability was introduced in versions: 9.12.0, 10.3.0, 10.4.0, and 10.5.0 of Jira Core Data Center and Server 5.12.0, 10.3.0, 10.4.0, and 10.5.0 of Jira Service Management Data Center and Server This PrivEsc (Privilege Escalation) vulnerability, with a CVSS Score of 7.2, allows an attacker to perform actions as a higher-privileged user. Atlassian recommends that Jira Core Data Center and Server and Jira Service Management Data Center and Server customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Jira Core Data Center and Server 9.12: Upgrade to a release greater than or equal to 9.12.20 Jira Service Management Data Center and Server 5.12: Upgrade to a release greater than or equal to 5.12.20 Jira Core Data Center 10.3: Upgrade to a release greater than or equal to 10.3.5 Jira Service Management Data Center 10.3: Upgrade to a release greater than or equal to 10.3.5 Jira Core Data Center 10.4: Upgrade to a release greater than or equal to 10.6.0 Jira Service Management Data Center 10.4: Upgrade to a release greater than or equal to 10.6.0 Jira Core Data Center 10.5: Upgrade to a release greater than or equal to 10.5.1 Jira Service Management Data Center 10.5: Upgrade to a release greater than or equal to 10.5.1 See the release notes. You can download the latest version of Jira Core Data Center and Jira Service Management Data Center from the download center. This vulnerability was reported via our Atlassian (Internal) program.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
Low (AC:L)
No specialized conditions required
Privileges Required
Low (PR:L)
Standard user access required
User Interaction
None (UI:N)
Zero human interaction required
Scope
Unchanged (S:U)
Confined to same security context
Confidentiality
High (C:H)
Total information disclosure
Integrity
High (I:H)
Total modification of target system
Availability
High (A:H)
Total denial of service or shutdown

🎯 Affected Versions Matrix

Affected Product atlassian / jira_data_center
Affected Versions *
Weakness Enumeration CWE-284

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2025-22157 impacting atlassian jira_data_center.

⚡ Nuclei Detection Template (YAML) cve-2025-22157.yaml
id: cve-2025-22157

info:
  name: atlassian jira_data_center - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: high
  description: |
    Automated signature & scanner for CVE-2025-22157 affecting atlassian jira_data_center.
    Evaluation: This High severity PrivEsc (Privilege Escalation) vulnerability was introduced in versions:

9.12.0, 10.3.0, 10.4.0, and 10.5.0 of Jira Core Data Cent...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2025-22157
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
    cvss-score: 8.8
    cve-id: CVE-2025-22157
    cwe-id: CWE-284
  tags: cve,cve-2025-22157,atlassian,jira_data_center,high

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "jira_data_center"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2025-22157.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2025-22157
# Target: atlassian jira_data_center | CVSS: 8.8 (HIGH)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2025-22157 (atlassian jira_data_center)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against atlassian jira_data_center scope (*).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2025-22157.sh
# Recommended Remediation & Patching Commands for CVE-2025-22157
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install jira_data_center 2>/dev/null || \
sudo dnf upgrade jira_data_center 2>/dev/null || \
sudo yum update jira_data_center

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i jira_data_center 2>/dev/null || rpm -qa | grep -i jira_data_center

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

🔗 Verified Technical References

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2025-22157 in atlassian jira_data_center?

Review vendor-specific security notices and update atlassian jira_data_center packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2025-22157?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2025-22157?

CVE-2025-22157 is classified with a CVSS 3.1 Base Score of 8.8 (HIGH). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
8.8
HIGH SEVERITY
CVE ID CVE-2025-22157
Weakness CWE-284
Vendor atlassian
Product jira_data_center
Published 2025-05-20
Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H