LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13404: The VerifyPopServerConnection resource in Atlassian Jira before version 7.6.10, from version 7.7.0 before v...

The VerifyPopServerConnection resource in Atlassian Jira before version 7.6.10, from version 7.7.0 before version 7.7.5, from version 7.8.0 before version 7.8.5, from version 7.9.0 before version 7.9.3, from version 7.10.0 before version 7.10.3, from version 7.11.0 before version 7.11.3, from version 7.12.0 before version 7.12.3, and from version 7.13.0 before version 7.13.1 allows remote attackers who have administrator rights to determine the existence of internal hosts & open ports and in some cases obtain service information from internal network resources via a Server Side Request Forgery (SSRF) vulnerability.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-13404 is an Atlassian Jira SSRF issue. A Jira administrator could use the POP server connection verification feature to test internal hosts and ports, and sometimes retrieve service information. The main business risk is internal reconnaissance from a trusted Jira system, especially if administrator access is broadly held or compromised.

Executive priority

Treat this as a controlled but real internal exposure issue. It is not described as unauthenticated or actively exploited, but Jira administrators or compromised admin accounts could use it to map internal services. Prioritize upgrade validation and administrator access review.

Technical view

The vulnerable VerifyPopServerConnection resource in affected Jira versions can be abused by remote attackers with administrator rights to make server-side requests toward internal network resources. Reported impact is determining whether internal hosts and ports exist, with possible service information disclosure in some cases.

Likely exposure

Exposure is most likely in affected Atlassian Jira deployments where users with administrator rights can access POP server connection verification. The source bundle lists multiple vulnerable 7.x branches before fixed patch releases.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not marked KEV. The attacker requirement is significant: administrator rights are needed. Risk increases if Jira admin accounts are shared, weakly protected, or reachable through compromised credentials.

Researcher notes

Evidence is limited to the CVE description and Atlassian issue reference. No CVSS, CWE, exploit confirmation, or detailed patch notes are included in the supplied bundle. Avoid assuming broader Jira products, unauthenticated reachability, or public exploit availability without additional vendor or threat-intelligence confirmation.

Mitigation direction

  • Upgrade Jira to the fixed release for the deployed branch.
  • Check Atlassian JRASERVER-68527 for vendor-specific remediation guidance.
  • Restrict Jira administrator access to necessary personnel only.
  • Limit outbound network access from Jira to required destinations.
  • Review internal service exposure reachable from the Jira server.

Validation and detection

  • Inventory Jira versions and compare against affected 7.x ranges.
  • Confirm Jira is at or above the fixed patch level for its branch.
  • Review who has Jira administrator rights and remove unnecessary access.
  • Check whether Jira can reach sensitive internal hosts or ports.
  • Review logs for unusual POP connection verification activity.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-13404 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AtlassianJiraunspecified, 7.7.0, unspecified, 7.8.0, unspecified, 7.9.0, unspecified, 7.10.0, unspecified, 7.11.0, unspecified, 7.12.0, unspecified, 7.13.0, unspecifiedListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.