Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-638 (未能使用完整仲裁) — Vulnerability Class 1

1 vulnerabilities classified as CWE-638 (未能使用完整仲裁). AI Chinese analysis included.

CWE-638 represents a critical access control weakness where software fails to verify permissions on every interaction with a protected resource. This flaw typically arises when developers assume that an initial authorization check remains valid for the entire session, ignoring potential privilege changes or context shifts. Attackers exploit this by manipulating requests after the initial validation, such as altering parameters in subsequent API calls or exploiting race conditions where state changes occur between checks. To mitigate this risk, developers must implement complete mediation by enforcing access control checks at every single point of resource access, regardless of prior validations. This approach ensures that the system continuously verifies the entity’s current rights, thereby preventing unauthorized actions even if privileges have been revoked or modified since the initial request.

MITRE CWE Description
The product does not perform access checks on a resource every time the resource is accessed by an entity, which can create resultant weaknesses if that entity's rights or privileges change over time.
Common Consequences (1)
Integrity, Confidentiality, Availability, Access Control, OtherGain Privileges or Assume Identity, Execute Unauthorized Code or Commands, Bypass Protection Mechanism, Read Application Data, Other
A user might retain access to a critical resource even after privileges have been revoked, possibly allowing access to privileged functionality or sensitive information, depending on the role of the resource.
Mitigations (2)
Architecture and DesignInvalidate cached privileges, file handles or descriptors, or other access credentials whenever identities, processes, policies, roles, capabilities or permissions change. Perform complete authentication checks before accepting, caching and reusing data, dynamic content and code (scripts). Avoid caching access control decisions as much as possible.
Architecture and DesignIdentify all possible code paths that might access sensitive resources. If possible, create and use a single interface that performs the access checks, and develop code standards that require use of this interface.
Examples (2)
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.
When a developer begins to implement input validation for a web application, often the validation is performed in each area of the code that uses externally-controlled input. In complex applications with many inputs, the developer often misses a parameter here or a cookie there. One frequently-applied solution is to centralize all input validation, store these validated inputs in a separate data s…

Vulnerabilities classified as CWE-638 (未能使用完整仲裁) represent 1 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.