CVE-2018-20238

HIGHNVD 8.18.1—

8.1

Various rest resources in Atlassian Crowd before version 3.2.7 and from version 3.3.0 before version 3.3.4 allow remote attackers to authenticate using an expired user session via an insufficient session expiration vulnerability.

CVSS v3: 8.1
EG Score: 8.1(medium)
EPSS: 42.6%
KEV: Not listed

Published

February 13, 2019

Last Modified

November 21, 2024

References (4)

security@atlassianhttp://www.securityfocus.com/bid/107036
security@atlassianhttps://jira.atlassian.com/browse/CWD-5361
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/107036
af854a3a-2127-422b-91ae-364da2661108https://jira.atlassian.com/browse/CWD-5361

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-384Session Fixation

Data Freshness Timeline

(refreshed 9× in last 7d / 19× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-04 13:10 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 22:32 UTCEG score recompute
2026-05-27 22:32 UTCGHSA enrichment
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2018-20238?

CVE-2018-20238 is a high vulnerability published on February 13, 2019. Various rest resources in Atlassian Crowd before version 3.2.7 and from version 3.3.0 before version 3.3.4 allow remote attackers to authenticate using an expired user session via an insufficient session expiration vulnerability.

When was CVE-2018-20238 disclosed?

CVE-2018-20238 was first published in the National Vulnerability Database on February 13, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2018-20238 actively exploited?

CVE-2018-20238 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 42.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2018-20238?

CVE-2018-20238 has a CVSS v3 base score of 8.1 (NVD).

How do I remediate CVE-2018-20238?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-20238, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-20238

Explore →

Is Your Infrastructure Affected by CVE-2018-20238?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2018-20238

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2018-20238?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)