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

CVE-2020-25019 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:N/I:H/A:N. EPSS exploitation probability: 1.0%.

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

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

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

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

Meet Electron CVE-2020-25019

HIGH

Insufficient Verification of Data Authenticity (CWE-345)

2020-08-29 cve@mitre.org

Information Disclosure Meet Electron

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:N/I:H/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:N/I:H/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Lifecycle Timeline

CVE Published

Aug 29, 2020 - 17:15 nvd

HIGH 7.5

DescriptionNVD

jitsi-meet-electron (aka Jitsi Meet Electron) before 2.3.0 calls the Electron shell.openExternal function without verifying that the URL is for an http or https resource, in some circumstances.

AnalysisAI

jitsi-meet-electron (aka Jitsi Meet Electron) before 2.3.0 calls the Electron shell.openExternal function without verifying that the URL is for an http or https resource, in some circumstances. 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 under CWE-345. jitsi-meet-electron (aka Jitsi Meet Electron) before 2.3.0 calls the Electron shell.openExternal function without verifying that the URL is for an http or https resource, in some circumstances. Affected products include: Jitsi Meet Electron. Version information: before 2.3.0.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.