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

CVE-2022-1713 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 9.2%.

Is there a public PoC exploit available for CVE-2022-1713?

Yes, a public proof-of-concept exploit is available for CVE-2022-1713. Prioritise patching immediately. EPSS: 9.2%.

Is there a patch available for CVE-2022-1713?

Yes, a patch is available for CVE-2022-1713. Update the affected software to the latest version immediately.

Drawio CVE-2022-1713

HIGH

Server-Side Request Forgery (SSRF) (CWE-918)

2022-05-16 security@huntr.dev

SSRF Drawio

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

May 16, 2022 - 15:15 nvd

HIGH 7.5

DescriptionNVD

SSRF on /proxy in GitHub repository jgraph/drawio prior to 18.0.4. An attacker can make a request as the server and read its contents. This can lead to a leak of sensitive information.

AnalysisAI

SSRF on /proxy in GitHub repository jgraph/drawio prior to 18.0.4. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as Server-Side Request Forgery (SSRF) (CWE-918), which allows attackers to make the server perform requests to unintended internal or external resources. SSRF on /proxy in GitHub repository jgraph/drawio prior to 18.0.4. An attacker can make a request as the server and read its contents. This can lead to a leak of sensitive information. Affected products include: Diagrams Drawio. Version information: prior to 18.0.4..

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate and allowlist destination URLs, block requests to internal networks, use network segmentation.