The product violates well-established principles for secure design.

What CVEs are caused by CWE-657?

16 recorded CVEs are attributed to CWE-657, including CVE-2026-39888, CVE-2026-30792, CVE-2023-29320.

What are the consequences of CWE-657?

Exploiting CWE-657 can lead to: Other.

Is CWE-657 actively exploited?

16 recorded CVEs are caused by CWE-657; none are currently in CISA's KEV catalog of actively exploited flaws.

CWE-657: Violation of Secure Design Principles

Code examples

Illustrative examples from MITRE showing how the weakness appears in code.

Switches may revert their functionality to that of hubs when the table used to map ARP information to the switch interface overflows, such as when under a spoofing attack. This results in traffic being broadcast to an eavesdropper, instead of being sent only on the relevant switch interface. To mitigate this type of problem, the developer could limit the number of ARP entries that can be recorded for a given switch interface, while other interfaces may keep functioning normally. Configuration options can be provided on the appropriate actions to be taken in case of a detected failure, but safe defaults should be used.

The IPSEC specification is complex, which resulted in bugs, partial implementations, and incompatibilities between vendors.

When executable library files are used on web servers, which is common in PHP applications, the developer might perform an access check in any user-facing executable, and omit the access check from the library file itself. By directly requesting the library file (CWE-425), an attacker can bypass this access check.

Single sign-on technology is intended to make it easier for users to access multiple resources or domains without having to authenticate each time. While this is highly convenient for the user and attempts to address problems with psychological acceptability, it also means that a compromise of a user's credentials can provide immediate access to all other resources or domains.

The design of TCP relies on the secrecy of Initial Sequence Numbers (ISNs), as originally covered in CVE-1999-0077 [REF-542]. If ISNs can be guessed (due to predictability, CWE-330) or sniffed (due to lack of encryption during transmission, CWE-312), then an attacker can hijack or spoof connections. Many TCP implementations have had variations of this problem over the years, including CVE-2004-0641, CVE-2002-1463, CVE-2001-0751, CVE-2001-0328, CVE-2001-0288, CVE-2001-0163, CVE-2001-0162, CVE-2000-0916, and CVE-2000-0328.

The "SweynTooth" vulnerabilities in Bluetooth Low Energy (BLE) software development kits (SDK) were found to affect multiple Bluetooth System-on-Chip (SoC) manufacturers. These SoCs were used by many products such as medical devices, Smart Home devices, wearables, and other IoT devices. [REF-1314] [REF-1315]

CWE-657: Violation of Secure Design Principles

Overview

Real-world CVEs

Common consequences

How it happens

When it is introduced

Code examples

Illustrative examples

Terminology & mappings

Mapped taxonomies

Frequently asked questions

What is CWE-657?

What CVEs are caused by CWE-657?

What are the consequences of CWE-657?

Is CWE-657 actively exploited?

References

Stay ahead of CWE-657

Overview

Real-world CVEs

Common consequences

How it happens

When it is introduced

Code examples

Illustrative examples

Related weaknesses

Parent

Child

Terminology & mappings

Mapped taxonomies

Frequently asked questions

What is CWE-657?

What CVEs are caused by CWE-657?

What are the consequences of CWE-657?

Is CWE-657 actively exploited?

References

Stay ahead of CWE-657