CVE-2017-18036

MEDIUMNVD 4.34.3—Trending — 3 sources updated this week

4.3

The Github repository importer in Atlassian Bitbucket Server before version 5.3.0 allows remote attackers to determine if a service they could not otherwise reach has open ports via a Server Side Request Forgery (SSRF) vulnerability.

CVSS v3: 4.3
EG Score: 4.3(medium)
EPSS: 35.2%
KEV: Not listed

Published

February 2, 2018

Last Modified

November 21, 2024

References (4)

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

Weakness Classification(1)

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

CWE-918Server-Side Request Forgery (SSRF)

Data Freshness Timeline

(refreshed 12× 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-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 22:28 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-28 11:58 UTCEG score recompute
2026-05-28 11:58 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
2026-05-24 07:06 UTCOSV refresh

Frequently asked(5)

What is CVE-2017-18036?

CVE-2017-18036 is a medium vulnerability published on February 2, 2018. The Github repository importer in Atlassian Bitbucket Server before version 5.3.0 allows remote attackers to determine if a service they could not otherwise reach has open ports via a Server Side Request Forgery (SSRF) vulnerability.

When was CVE-2017-18036 disclosed?

CVE-2017-18036 was first published in the National Vulnerability Database on February 2, 2018, 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-2017-18036 actively exploited?

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

What is the CVSS score of CVE-2017-18036?

CVE-2017-18036 has a CVSS v3 base score of 4.3 (NVD).

How do I remediate CVE-2017-18036?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-18036, 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-2017-18036

Explore →

Is Your Infrastructure Affected by CVE-2017-18036?

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

Start Free Scan →Browse All CVEs

CVE-2017-18036

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2017-18036?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)