CWEweakness

CWE-710 Improper Adherence to Coding Standards

Official page ↗
Abstraction
Pillar
Structure
Simple
Status
Incomplete
Languages
Not Language-Specific
CWE version
5.0

Description

The product does not follow certain coding rules for development.

Common consequences

• Other: Varies by Context — This can lead to resultant weaknesses or increase the severity of the associated vulnerabilities.

Potential mitigations

• [Policy] Select and require coding standards. Ensure that they include security concerns. • [Implementation] Closely follow coding standards, possibly enforcing them upon checkin of the code into a source control system or with periodic analyses.

Detection methods

• Automated Static Analysis: Automated tools can detect violations of many code standards.

Related

Referenced by CVE · weakness (8)

  • CVE-2026-76285 As part of Cisco's ongoing commitment to proactive security and product quality, Cisco has conducted a comprehensive internal security… vulnerability
  • CVE-2026-20334 As part of Cisco's ongoing commitment to proactive security and product quality, the Cisco Secure Adaptive Security Appliance Software,… vulnerability
  • CVE-2025-0007 Insufficient validation within Xilinx Run Time framework could allow a local attacker to escalate privileges from user space to kernel… vulnerability
  • CVE-2023-30961 Palantir Gotham was found to be vulnerable to a bug where under certain circumstances, the frontend could have applied an incorrect… vulnerability
  • CVE-2021-27501 Philips Vue PACS versions 12.2.x.x and prior does not follow certain coding rules for development, which can lead to resultant weaknesses… vulnerability
  • CVE-2021-33528 In Weidmueller Industrial WLAN devices in multiple versions an exploitable privilege escalation vulnerability exists in the iw_console… vulnerability
  • CVE-2020-1613 A vulnerability in the BGP FlowSpec implementation may cause a Juniper Networks Junos OS device to terminate an established BGP session… vulnerability
  • CVE-2020-1603 Specific IPv6 packets sent by clients processed by the Routing Engine (RE) are improperly handled. vulnerability

Referenced by CWE · child of (28)

  • CWE-1041 Use of Redundant Code weakness
  • CWE-1044 Architecture with Number of Horizontal Layers Outside of Expected Range weakness
  • CWE-1048 Invokable Control Element with Large Number of Outward Calls weakness
  • CWE-1059 Insufficient Technical Documentation weakness
  • CWE-1061 Insufficient Encapsulation weakness
  • CWE-1066 Missing Serialization Control Element weakness
  • CWE-1068 Inconsistency Between Implementation and Documented Design weakness
  • CWE-1076 Insufficient Adherence to Expected Conventions weakness
  • CWE-1092 Use of Same Invokable Control Element in Multiple Architectural Layers weakness
  • CWE-1093 Excessively Complex Data Representation weakness
  • CWE-1101 Reliance on Runtime Component in Generated Code weakness
  • CWE-1120 Excessive Code Complexity weakness
  • CWE-1126 Declaration of Variable with Unnecessarily Wide Scope weakness
  • CWE-1127 Compilation with Insufficient Warnings or Errors weakness
  • CWE-1164 Irrelevant Code weakness
  • CWE-1177 Use of Prohibited Code weakness
  • CWE-1209 Failure to Disable Reserved Bits weakness
  • CWE-1357 Reliance on Insufficiently Trustworthy Component weakness
  • CWE-476 NULL Pointer Dereference weakness
  • CWE-477 Use of Obsolete Function weakness
  • CWE-484 Omitted Break Statement in Switch weakness
  • CWE-489 Active Debug Code weakness
  • CWE-570 Expression is Always False weakness
  • CWE-571 Expression is Always True weakness
  • CWE-573 Improper Following of Specification by Caller weakness
  • CWE-657 Violation of Secure Design Principles weakness
  • CWE-684 Incorrect Provision of Specified Functionality weakness
  • CWE-758 Reliance on Undefined, Unspecified, or Implementation-Defined Behavior weakness

Referenced by CWE · has member (1)

  • CWE-1000 Complete Weakness Hierarchy view