Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2022-1592: SSRF in clinical-genomics/scout

Published May 5, 2022 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.2High · v3.1
EPSS1.3%72nd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Clinical-Genomics
IdentifiersCVE-2022-1592CWE-918 · Server-Side Request Forgery (SSRF)

CVE-2022-1592 is a server-side request forgery (SSRF) vulnerability in the Scout application from the GitHub repository clinical-genomics/scout, affecting versions prior to 4.42. The available description indicates that attacker-controlled input can cause the application to issue arbitrary outbound requests on the attacker's behalf. This can be abused to target attacker-chosen external or internal resources, including private network locations not directly reachable by the attacker. The provided information does not identify the exact vulnerable function or code path.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to coerce the vulnerable Scout server into making arbitrary HTTP requests. This can enable access to internal services, interaction with private network resources, retrieval of sensitive data exposed to the server, and use of the application as a pivot for network reconnaissance. The source description also indicates possible phishing-related abuse, cookie theft scenarios, requests into private areas, and potential XSS-related follow-on effects depending on how fetched content is handled elsewhere in the application.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict the application's outbound network access to only required destinations, block access from the application host to internal RFC1918 space and cloud metadata services where feasible, and place egress filtering controls at the host or network boundary. Validate and sanitize any user-supplied URLs, enforce protocol restrictions, and implement allowlists for permitted remote hosts. Monitor outbound requests from the application for anomalous destinations and patterns indicative of SSRF exploitation.

Remediation

Patch, then assume compromise.

Upgrade clinical-genomics/scout to version 4.42 or later, as versions prior to 4.42 are affected according to the provided content. In addition, review and harden any functionality that fetches user-supplied URLs by enforcing strict allowlists, validating schemes and destinations, disabling access to internal address ranges and metadata endpoints, and ensuring fetched content is not reflected or rendered in a way that could enable secondary client-side attacks.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Clinical-GenomicsScoutapplication
FAQ

Frequently asked questions

Is CVE-2022-1592 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2022-1592 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2022-1592?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2022-1592.
Is there a patch for CVE-2022-1592?
Upgrade clinical-genomics/scout to version 4.42 or later, as versions prior to 4.42 are affected according to the provided content. In addition, review and harden any functionality that fetches user-supplied URLs by enforcing strict allowlists, validating schemes and destinations, disabling access to internal address ranges and metadata endpoints, and ensuring fetched content is not reflected or rendered in a way that could enable secondary client-side attacks.
What products are affected by CVE-2022-1592?
Clinical-Genomics Scout.
How severe is CVE-2022-1592?
CVE-2022-1592 has a CVSS v3.1 score of 8.2 (High) and an EPSS score of 1.3% (72nd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.