CVE-2019-16889

Exp

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.

Published: 2019-09-25 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2019-16889 is rated High Exploit Risk (71.9/100): CVSS High severity, with high exploitation likelihood (EPSS 5.09%, 91th percentile). Core evidence: 2 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2019-16889

EDB-ID Source Kind Published Link
nvd_ref exploit_tag Exploit-DB ↗
nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2019-16889

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 11.49% 5.09% -6.40%
2 2025-11-21 9.05% 11.49% +2.44%
3 2025-11-18 9.05%

Full EPSS history (15 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-16889

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9 3.6 [email protected]
7.8 2.0 HIGH
AV:N/AC:L/Au:N/C:N/I:N/A:C Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:C)
Complete availability impact.
10.0 6.9 [email protected]

Weakness enumeration for CVE-2019-16889

Affected software / configurations for CVE-2019-16889

Vendor Product Version Raw CPE
ui er-x_firmware < 2.0.3 cpe:2.3:o:ui:er-x_firmware:*:*:*:*:*:*:*:*
ui er-x-sfp_firmware < 2.0.3 cpe:2.3:o:ui:er-x-sfp_firmware:*:*:*:*:*:*:*:*
ui ep-r6_firmware < 2.0.3 cpe:2.3:o:ui:ep-r6_firmware:*:*:*:*:*:*:*:*
ui erlite-3_firmware < 2.0.3 cpe:2.3:o:ui:erlite-3_firmware:*:*:*:*:*:*:*:*
ui erpoe-5_firmware < 2.0.3 cpe:2.3:o:ui:erpoe-5_firmware:*:*:*:*:*:*:*:*
ui er-8_firmware < 2.0.3 cpe:2.3:o:ui:er-8_firmware:*:*:*:*:*:*:*:*
ui erpro-8_firmware < 2.0.3 cpe:2.3:o:ui:erpro-8_firmware:*:*:*:*:*:*:*:*
ui ep-r8_firmware < 2.0.3 cpe:2.3:o:ui:ep-r8_firmware:*:*:*:*:*:*:*:*
ui er-4_firmware < 2.0.3 cpe:2.3:o:ui:er-4_firmware:*:*:*:*:*:*:*:*
ui er-6p_firmware < 2.0.3 cpe:2.3:o:ui:er-6p_firmware:*:*:*:*:*:*:*:*
ui er-12_firmware < 2.0.3 cpe:2.3:o:ui:er-12_firmware:*:*:*:*:*:*:*:*
ui er-8-xg_firmware < 2.0.3 cpe:2.3:o:ui:er-8-xg_firmware:*:*:*:*:*:*:*:*

References for CVE-2019-16889

cvelogic Threat Intelligence