CVE-2014-0769 — Festo CECX-X-(C1/M1) Controller Improper Authentication

The Festo CECX-X-C1 Modular Master Controller with CoDeSys and CECX-X-M1 Modular Controller with CoDeSys and SoftMotion do not require authentication for connections to certain TCP ports, which allows remote attackers to (1) modify the configuration via a request to the debug service on port 4000 or (2) delete log entries via a request to the log service on port 4001.

Published Apr 25, 2014Updated Jul 2, 2025Sources: cvelistV5, icscert

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

chance of exploitation in 30 days

Affects

festo

2 products listed

CVSS base

9.3

CRITICAL

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

festo

Products (2)

cecx x c1 modular master controller with codesyscecx x m1 modular controller with codesys and softmotion

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.3	CVSS 2.0	CRITICAL	—	—	cvelistV5

Weakness & attack patterns

CWE-287

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

T1548Abuse Elevation Control Mechanism
T1040Network Sniffing
T1185Browser Session Hijacking

References

2 on the record

www.cisa.gov/news-events/ics-advisories/icsa-14-084-01
reference
ics-cert.us-cert.gov/advisories/ICSA-14-084-01
x_refsource_MISC, x_transferred

Elsewhere on this site

festoevery CVE for this vendor
CWE-287other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.