The WebUI of PHOENIX CONTACT FL SWITCH 3xxx, 4xxx, 48xx versions 1.0 to 1.34 is vulnerable to a denial-of-service attack by making more than
The WebUI of PHOENIX CONTACT FL SWITCH 3xxx, 4xxx, 48xx versions 1.0 to 1.34 is vulnerable to a denial-of-service attack by making more than 120 connections.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- May 7, 2019
- Updated
- Jun 16, 2026
- EPSS
- 2.2% · 82th percentile
- CWE
- CWE-400
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.2%
CNA vs NVD score
- NVD
- 7.5
- CNA · mitre
- 7.5
- agree
CVSS:3.0/AC:L/AV:N/A:H/C:N/I:N/PR:N/S:U/UI:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| phoenixcontact | fl switch 3005 firmware | cpe:2.3:o:phoenixcontact:fl_switch_3005_firmware |
| phoenixcontact | fl switch 3005 | cpe:2.3:h:phoenixcontact:fl_switch_3005 |
| phoenixcontact | fl switch 3005t firmware | cpe:2.3:o:phoenixcontact:fl_switch_3005t_firmware |
| phoenixcontact | fl switch 3005t | cpe:2.3:h:phoenixcontact:fl_switch_3005t |
| phoenixcontact | fl switch 3004t-fx firmware | cpe:2.3:o:phoenixcontact:fl_switch_3004t-fx_firmware |
| phoenixcontact | fl switch 3004t-fx | cpe:2.3:h:phoenixcontact:fl_switch_3004t-fx |
| phoenixcontact | fl switch 3004t-fx st firmware | cpe:2.3:o:phoenixcontact:fl_switch_3004t-fx_st_firmware |
| phoenixcontact | fl switch 3004t-fx st | cpe:2.3:h:phoenixcontact:fl_switch_3004t-fx_st |
| phoenixcontact | fl switch 3008 firmware | cpe:2.3:o:phoenixcontact:fl_switch_3008_firmware |
| phoenixcontact | fl switch 3008 | cpe:2.3:h:phoenixcontact:fl_switch_3008 |
| phoenixcontact | fl switch 3008t firmware | cpe:2.3:o:phoenixcontact:fl_switch_3008t_firmware |
| phoenixcontact | fl switch 3008t | cpe:2.3:h:phoenixcontact:fl_switch_3008t |
and 46 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- phoenixcontact fl switch 3004t-fx firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 3004t-fx st firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 3005 firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 3005t firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 3006t-2fx firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 3006t-2fx sm firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 3006t-2fx st firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 3008 firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 3008t firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 3012e-2fx sm firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 3012e-2sfx firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 3016 firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 3016e firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 3016t firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 4000t-8poe-2sfp-r firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 4008t-2gt-3fx sm firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 4008t-2gt-4fx sm firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 4008t-2sfp firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 4012t 2gt 2fx firmware1.0 and later · up to 1.34 inclusive
- phoenixcontact fl switch 4012t-2gt-2fx st firmware1.0 and later · up to 1.34 inclusive
Same product
phoenixcontact: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-13990The WebUI of PHOENIX CONTACT FL SWITCH 3xxx, 4xxx, 48xx versions prior to 1.35 is vulnerable to brute-force attacks, because of Improper Res40Plan
- CVE-2017-16743An Improper Authorization issue was discovered in PHOENIX CONTACT FL SWITCH 3xxx, 4xxx, and 48xxx Series products running firmware Version 140Plan
- CVE-2018-13992The WebUI of PHOENIX CONTACT FL SWITCH 3xxx, 4xxx, 48xx versions 1.0 to 1.34 allows for plaintext transmission (HTTP) of user credentials by39Monitor
- CVE-2018-10731All Phoenix Contact managed FL SWITCH 3xxx, 4xxx, 48xx products running firmware version 1.0 to 1.33 are prone to buffer overflows when hand37Monitor
- CVE-2018-10730All Phoenix Contact managed FL SWITCH 3xxx, 4xxx, 48xx products running firmware version 1.0 to 1.33 are prone to OS command injection.37Monitor
- CVE-2018-13993The WebUI of PHOENIX CONTACT FL SWITCH 3xxx, 4xxx, 48xx versions 1.0 to 1.34 is prone to CSRF.35Monitor
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
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
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-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) { return node.children.map(expand);}Fixed
const MAX_DEPTH = 32;function expand(node, depth = 0) { if (depth > MAX_DEPTH) throw new Error("too deep"); return node.children.map((c) => expand(c, depth + 1));}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
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.