SecOps SignalSecurity Intelligence Workspace
Loading collection status
Vulnerabilities/CVE-2020-15415Public Intelligence Dossier
Source: draytek · Limited verification•Last verified: •Collection Degraded
CVE-2020-15415ListedCRITICAL (raw)CVSS 9.8CWE-78

On DrayTek Vigor3900, Vigor2960, and Vigor300B devices before 1.5.1, cgi-bin/mainfunction.cgi/cvmcfgupload allows remote command execution via shell metacharacters in a filename when the text/x-python-script content type is used, a different issue than CVE-2020-14472.

Published: 30 Jun 2020•Last updated: 17 Jun 2026, 08:26 AM IST•Source identifier: cve@mitre.org
Dossier completeness: source-provided sections 3 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Listed
Added30 Sept 2024
Due21 Oct 2024
RansomwareUnknown
CVSS score
9.8CRITICAL (raw)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Metric sourcenvd@nist.gov
EPSS probability
84.5%0.845
Percentile100th
Weakness type
CWE-78
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

On DrayTek Vigor3900, Vigor2960, and Vigor300B devices before 1.5.1, cgi-bin/mainfunction.cgi/cvmcfgupload allows remote command execution via shell metacharacters in a filename when the text/x-python-script content type is used, a different issue than CVE-2020-14472.

SOC priority

Immediate Attention

Actively exploited (source statement)

Yes

Publicly disclosed

Unknown

Risk basis: CISA KEV exploitation signal; CRITICAL severity; Known exploitation signal from CISA KEV or ransomware metadata; Source-confirmed exploitation or CISA KEV/ransomware metadata

Affected Products & Remediation

3 source-backed products
Affected products and versions (source)
  • draytek vigor3900 firmware · < 1.5.1 · NVD CPE · Source
  • draytek vigor2960 firmware · < 1.5.1 · NVD CPE · Source
  • draytek vigor300b firmware · < 1.5.1 · NVD CPE · Source
NVD applicability prerequisites: cpe:2.3:h:draytek:vigor3900:-:*:*:*:*:*:*:*, cpe:2.3:h:draytek:vigor2960:-:*:*:*:*:*:*:*, cpe:2.3:h:draytek:vigor300b:-:*:*:*:*:*:*:*. These are conditions, not proof that an environment is exposed or unaffected.
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

  • CISA KEV: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Listed
Exploited (source statement)
Yes
Publicly disclosed (source)
Unknown

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched kev-network-exposure (CVSS AV:N, CISA KEV Listed); command-injection (CWE-78)

Exposure

  1. Identify assets with the exact CVE and confirm the affected product/version against the advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · KEV listing raises urgency, but inventory is needed to establish local exposure. · Rule kev-network-exposure
  2. Identify installations of the affected product and compare versions with the advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · A weakness class does not establish local exposure. · Rule command-injection

Exploitation evidence

  1. Review relevant edge or application access logs for unusual requests around the advisory window.Telemetry: CommonSecurityLog · Log review is a hunting hypothesis; KEV listing alone does not show local exploitation. · Rule kev-network-exposure
Show more (2)

Exploitation evidence

  1. Review command interpreters spawned by the affected service or application.Telemetry: DeviceProcessEvents · Unexpected process lineage can support command-injection hunting. · Rule command-injection

Response

  1. Recheck the affected assets after the source-stated mitigation or update is applied.Telemetry: DeviceTvmSoftwareVulnerabilities · A follow-up inventory check verifies local remediation. · Rule kev-network-exposure

CISA KEV Record

Catalog entry
30 Sept 2024
Required action due
21 Oct 2024
Known ransomware use
Unknown

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Change History & Source Data

— No recorded material change

CNA / source
cve@mitre.org
Record status · verification
UPDATED · CISA KEV confirmed
CPE
cpe:2.3:o:draytek:vigor3900_firmware:*:*:*:*:*:*:*:*, cpe:2.3:h:draytek:vigor3900:-:*:*:*:*:*:*:*, cpe:2.3:o:draytek:vigor2960_firmware:*:*:*:*:*:*:*:*, cpe:2.3:h:draytek:vigor2960:-:*:*:*:*:*:*:*, cpe:2.3:o:draytek:vigor300b_firmware:*:*:*:*:*:*:*:*, cpe:2.3:h:draytek:vigor300b:-:*:*:*:*:*:*:*

Evidence & Provenance

4 public sources
CISA KEV CatalogAdded 2024-09-30draytek.comSource recordnvd.nist.govSource recordgithub.comSource record

Linked by the query's stored exact CVE association. Review required tables and validation status before use.

Detection Hunting Query
Target: DeviceTvmSoftwareVulnerabilities•Defender XDR
Detect endpoints exposed to CVE-2020-15415
Purpose: Exposure assessment (Category: Exposure Check)Why linked: Query metadata names CVE-2020-15415
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2020-15415"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc
Schema Checked · Not runtime validatedSource: SecOps Signal deterministic template · Limited verificationStatic screening: Passed structure and schema checks; tenant execution is not verified.
Open KQL Library

Looking up related community queries…

Loading related intelligence

Correlated briefings

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.