Ubiquiti EdgeMAX devices before 2.0.3 allow remote attackers to cause a denial of service (disk consumption) because *.cache files in /var/r
Noroxi assessment
Priority: Monitor (action score 32/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 5% (FIRST EPSS); higher than 92.1% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
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
- Sep 25, 2019
- Updated
- Jun 16, 2026
- EPSS
- 5.1% · 92th percentile
- CWE
- CWE-770
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 5.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| ui | er-x firmware | cpe:2.3:o:ui:er-x_firmware |
| ui | er-x | cpe:2.3:h:ui:er-x |
| ui | er-x-sfp firmware | cpe:2.3:o:ui:er-x-sfp_firmware |
| ui | er-x-sfp | cpe:2.3:h:ui:er-x-sfp |
| ui | ep-r6 firmware | cpe:2.3:o:ui:ep-r6_firmware |
| ui | ep-r6 | cpe:2.3:h:ui:ep-r6 |
| ui | erlite-3 firmware | cpe:2.3:o:ui:erlite-3_firmware |
| ui | erlite-3 | cpe:2.3:h:ui:erlite-3 |
| ui | erpoe-5 firmware | cpe:2.3:o:ui:erpoe-5_firmware |
| ui | erpoe-5 | cpe:2.3:h:ui:erpoe-5 |
| ui | er-8 firmware | cpe:2.3:o:ui:er-8_firmware |
| ui | er-8 | cpe:2.3:h:ui:er-8 |
and 12 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ui ep-r6 firmwarebefore 2.0.3
- ui ep-r8 firmwarebefore 2.0.3
- ui er-12 firmwarebefore 2.0.3
- ui er-4 firmwarebefore 2.0.3
- ui er-6p firmwarebefore 2.0.3
- ui er-8 firmwarebefore 2.0.3
- ui er-8-xg firmwarebefore 2.0.3
- ui er-x firmwarebefore 2.0.3
- ui er-x-sfp firmwarebefore 2.0.3
- ui erlite-3 firmwarebefore 2.0.3
- ui erpoe-5 firmwarebefore 2.0.3
- ui erpro-8 firmwarebefore 2.0.3
Same product
ui: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-2375Ubiquiti EdgeRouter X Web Management command injection32Monitor
- CVE-2023-2378Ubiquiti EdgeRouter X Web Management command injection31Monitor
- CVE-2023-2377Ubiquiti EdgeRouter X Web Management command injection31Monitor
- CVE-2023-2376Ubiquiti EdgeRouter X Web Management command injection31Monitor
- CVE-2023-2374Ubiquiti EdgeRouter X Web Management command injection31Monitor
- CVE-2023-2379Ubiquiti EdgeRouter X Web Service denial of service30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2019-12-09 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+74 d
- TodayOct 14, 2026+2576 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.