What is the CVSS score of CVE-2020-7739?

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

Is there a public PoC exploit available for CVE-2020-7739?

Yes, a public proof-of-concept exploit is available for CVE-2020-7739. Prioritise patching immediately. EPSS: 1.4%.

Is there a patch available for CVE-2020-7739?

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

Phantomjs Seo CVE-2020-7739

HIGH

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

2020-10-06 report@snyk.io

SSRF Phantomjs Seo

8.2

CVSS 3.1 · Vendor: snyk

Severity by source

Vendor (snyk) PRIMARY

8.2 HIGH

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

Primary rating from Vendor (snyk) · only source for this CVE.

CVSS VectorVendor: snyk

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

None

Lifecycle Timeline

CVE Published

Oct 06, 2020 - 15:15 cve.org

HIGH 8.2

DescriptionCVE.org

This affects all versions of package phantomjs-seo. It is possible for an attacker to craft a url that will be passed to a PhantomJS instance allowing for an SSRF attack.

AnalysisAI

This affects all versions of package phantomjs-seo. Rated high severity (CVSS 8.2), 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. This affects all versions of package phantomjs-seo. It is possible for an attacker to craft a url that will be passed to a PhantomJS instance allowing for an SSRF attack. Affected products include: Phantomjs-Seo Project Phantomjs-Seo.

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.