LiveActive security incident?Get immediate response
CVE Record

CVE-2020-37039: Frigate 2.02 - Denial Of Service

Frigate 2.02 contains a denial of service vulnerability that allows attackers to crash the application by sending oversized input to the command line interface. Attackers can generate a payload of 8000 repeated characters and paste it into the application's command line field to trigger an application crash.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-37039 is a denial-of-service flaw in WinFrigate Frigate 2 version 2.02. Oversized input to the application’s command-line field can crash the application, affecting availability rather than data confidentiality or integrity.

Executive priority

Treat this as a focused availability risk for legacy software. Prioritize if Frigate supports operational workflows or is reachable by untrusted users. Replacement or isolation may be more realistic than patching if no vendor fix exists.

Technical view

The sources describe improper resource control/input handling, mapped to CWE-770, causing Frigate 2.02 to crash when oversized CLI input is submitted. CVSS 3.1 is 7.5, with availability impact high. The provided evidence does not identify a vendor patch.

Likely exposure

Exposure is likely limited to environments still running WinFrigate Frigate 2.02. Risk is higher where untrusted users can interact with the application’s command-line field or any interface that passes input to it.

Exploitation context

A public ExploitDB entry exists, but the source bundle does not show CISA KEV listing or confirmed active exploitation. The described impact is application crash, not code execution or data theft.

Researcher notes

The record’s CVSS vector indicates network attack complexity, while the description centers on a command-line field. Validate actual exposure before rating internal risk. Do not assume broader Frigate versions are affected beyond 2.02 based on the provided sources.

Mitigation direction

  • Identify and retire Frigate 2.02 installations where possible.
  • Check vendor or maintainer guidance for any supported update or replacement.
  • Restrict access to the application to trusted users only.
  • Avoid exposing Frigate interfaces to untrusted networks.
  • Use monitoring to alert on repeated application crashes.

Validation and detection

  • Inventory endpoints and servers for WinFrigate Frigate 2.02.
  • Confirm whether the application is still business-critical.
  • Review access paths to any command-line input field.
  • Check logs for unexplained Frigate crashes or restarts.
  • Document compensating controls if no update is available.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-770: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-37039 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2020-37039Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WinFrigateFrigate 22.02Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-770 · source CWE mapping

Allocation of Resources Without Limits or Throttling

Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.