CVE-2022-0249

LOWNVD 3.19.1▲

3.1

A vulnerability was discovered in GitLab starting with version 12. GitLab was vulnerable to a blind SSRF attack since requests to shared address space were not blocked.

CVSS v3: 3.1
EG Score: 9.1(medium)
EPSS: 46.2%
KEV: Not listed

Published

March 28, 2022

Last Modified

November 21, 2024

References (6)

cve@gitlabhttps://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-0249.json
cve@gitlabhttps://gitlab.com/gitlab-org/gitlab/-/issues/29395
cve@gitlabhttps://hackerone.com/reports/579934
af854a3a-2127-422b-91ae-364da2661108https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-0249.json
af854a3a-2127-422b-91ae-364da2661108https://gitlab.com/gitlab-org/gitlab/-/issues/29395
af854a3a-2127-422b-91ae-364da2661108https://hackerone.com/reports/579934

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 10× 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:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 13:43 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-26 00:57 UTCEG score recompute
2026-05-26 00:57 UTCGHSA enrichment
2026-05-24 01:07 UTCOSV refresh

Frequently asked(5)

What is CVE-2022-0249?

CVE-2022-0249 is a low vulnerability published on March 28, 2022. A vulnerability was discovered in GitLab starting with version 12. GitLab was vulnerable to a blind SSRF attack since requests to shared address space were not blocked.

When was CVE-2022-0249 disclosed?

CVE-2022-0249 was first published in the National Vulnerability Database on March 28, 2022, 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-2022-0249 actively exploited?

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

What is the CVSS score of CVE-2022-0249?

CVE-2022-0249 has a CVSS v3 base score of 3.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.1.

How do I remediate CVE-2022-0249?

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

Explore →

Is Your Infrastructure Affected by CVE-2022-0249?

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

Start Free Scan →Browse All CVEs

CVE-2022-0249

📅 Published

🔄 Last Modified

🔗 References (6)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2022-0249?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(5)

Related CVEs(same CWE)