LiveActive security incident?Get immediate response
CVE Record

CVE-2019-16889: Ubiquiti EdgeMAX devices before 2.0.3 allow remote attackers to cause a denial of service (disk consumption...

Ubiquiti EdgeMAX devices before 2.0.3 allow remote attackers to cause a denial of service (disk consumption) because *.cache files in /var/run/beaker/container_file/ are created when providing a valid length payload of 249 characters or fewer to the beaker.session.id cookie in a GET header. The attacker can use a long series of unique session IDs.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-16889 is a denial-of-service issue in Ubiquiti EdgeMAX devices before version 2.0.3. A remote attacker could force repeated creation of cache files and consume disk space, potentially degrading or interrupting device operation. The public record does not provide CVSS scoring, and KEV does not list active exploitation.

Executive priority

Treat this as a moderate operational availability risk. It is not described as data theft or code execution, but affected edge network devices can become unreliable if disk space is exhausted. Prioritize internet-reachable or business-critical devices first.

Technical view

The flaw involves handling of the beaker.session.id cookie in GET requests. Supplying many unique valid-length session identifiers can cause *.cache files to be created under /var/run/beaker/container_file/, leading to disk consumption. Sources identify EdgeMAX devices before 2.0.3 as affected.

Likely exposure

Organizations using Ubiquiti EdgeMAX firmware older than 2.0.3 are the relevant exposure group. Risk is higher where the affected HTTP service is reachable by untrusted networks. The provided sources do not enumerate exact models or deployment conditions.

Exploitation context

The cited description supports remote denial-of-service through resource consumption. There is no KEV listing and no cited source in the bundle claiming active exploitation in the wild. No exploit steps are provided here.

Researcher notes

Evidence is strongest for the product family, version boundary, and disk-consumption mechanism. Public scoring, CWE mapping, exact model list, and confirmed exploitation status are not present in the supplied bundle, so validation should focus on firmware version and service exposure.

Mitigation direction

  • Upgrade affected EdgeMAX devices to firmware 2.0.3 or later where applicable.
  • Review Ubiquiti’s 2.0.3 release guidance before production rollout.
  • Restrict access to affected HTTP services to trusted administrators and networks.
  • Monitor device storage consumption until upgrades are complete.

Validation and detection

  • Inventory Ubiquiti EdgeMAX devices and record installed firmware versions.
  • Flag any EdgeMAX device running firmware earlier than 2.0.3.
  • Check whether affected HTTP services are reachable from untrusted networks.
  • Review device storage trends for unexplained cache-file growth.
Prepared
Confidence
medium
Sources
5

Public sources used

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.

cve · low confidence lookup

CVE-2019-16889 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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