BaseIncomplete

CWE-178Improper Handling of Case Sensitivity

Category: other

Description

The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results.

Common consequences· 1

  • Access Control — Bypass Protection Mechanism

Potential mitigations· 3

  • [Architecture and Design]Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
  • [Implementation]
  • [Implementation]Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.

References

  1. https://cwe.mitre.org/data/definitions/178.html

(incoming)10

TypeTargetConfidenceTier
VulnerabilityCVE-2025-59944cve-2025-599440%live
VulnerabilityCVE-2025-61593cve-2025-615930%live
VulnerabilityCVE-2026-22665cve-2026-226650%live
VulnerabilityCVE-2026-27587cve-2026-275870%live
VulnerabilityCVE-2026-27588cve-2026-275880%live
VulnerabilityCVE-2026-28292cve-2026-282920%live
VulnerabilityCVE-2026-32939cve-2026-329390%live
VulnerabilityCVE-2026-40453cve-2026-404530%live
VulnerabilityCVE-2026-47323cve-2026-473230%live
KEVEntryFortinet FortiOS SSL VPN Improper Authentication Vulnerabilitykev-cve-2020-128120%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Improper Handling of Parameters
CWE
Improper Handling of Undefined Parameters
CWE
Improper Handling of Unicode Encoding
CWE
Inconsistent Naming Conventions for Identifiers
CWE
Improper Handling of Invalid Use of Special Elements
CWE
Improper Handling of Undefined Values
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.