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

Goal: 1000 CNY · Raised: 1359 CNY

100%

CWE-306 (关键功能的认证机制缺失) — Vulnerability Class 1920

1920 vulnerabilities classified as CWE-306 (关键功能的认证机制缺失). AI Chinese analysis included.

CWE-306 represents a critical authentication weakness where software fails to verify user identity before executing sensitive operations or consuming substantial resources. Attackers typically exploit this vulnerability by directly invoking administrative endpoints, initiating high-cost processes, or accessing restricted data without valid credentials, effectively bypassing security controls. This oversight allows unauthorized users to perform actions intended only for authenticated individuals, leading to privilege escalation, data breaches, or denial of service through resource exhaustion. To mitigate this risk, developers must implement robust access control mechanisms that strictly enforce authentication checks on all critical functions. This involves integrating secure session management, validating tokens for every request, and applying the principle of least privilege to ensure that only verified users with appropriate permissions can trigger sensitive operations or consume significant system resources.

MITRE CWE Description
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
Common Consequences (1)
Access Control, Other Gain Privileges or Assume Identity, Varies by Context
Exposing critical functionality essentially provides an attacker with the privilege level of that functionality. The consequences will depend on the associated functionality, but they can range from reading or modifying sensitive data, accessing administrative or other privileged functionality, or p…
Mitigations (5)
Architecture and Design Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability. Identify all potential communication channels, or other means of interaction with the software, to ensure that all channels are appropriately protected, including those channels that are assumed to be access…
Architecture and Design For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
Architecture and Design Where possible, avoid implementing custom, "grow-your-own" authentication routines and consider using authentication capabilities as provided by the surrounding framework, operating system, or environment. These capabilities may avoid common weaknesses that are unique to authentication; support automatic auditing and tracking; and make it easier to provide a clear separation between authentication…
Architecture and Design Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator [REF-45].
Implementation, System Configuration, Operation When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data [REF-1297] [REF-1298] [REF-1302].
Examples (2)
In the following Java example the method createBankAccount is used to create a BankAccount object for a bank management application.
public BankAccount createBankAccount(String accountNumber, String accountType, String accountName, String accountSSN, double balance) { BankAccount account = new BankAccount(); account.setAccountNumber(accountNumber); account.setAccountType(accountType); account.setAccountOwnerName(accountName); account.setAccountOwnerSSN(accountSSN); account.setBalance(balance); return account; }
Bad · Java
private boolean isUserAuthentic = false; // authenticate user, // if user is authenticated then set variable to true // otherwise set variable to false public boolean authenticateUser(String username, String password) { ... } public BankAccount createNewBankAccount(String accountNumber, String accountType, String accountName, String accountSSN, double balance) { BankAccount account = null; if (isUserAuthentic) { account = new BankAccount(); account.setAccountNumber(accountNumber); account.setAccountType(accountType); account.setAccountOwnerName(accountName); account.setAccountOwnerSSN(accountS
Good · Java
In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these…
CVE ID Title CVSS Severity Published
CVE-2024-52285 Siemens SiPass Integrated 访问控制错误漏洞 — SiPass integrated AC5102 (ACC-G2) 5.3 Medium 2025-03-11
CVE-2025-23194 Missing Authentication check in SAP NetWeaver Enterprise Portal (OBN component) — SAP NetWeaver Enterprise Portal (OBN component) 5.3 Medium 2025-03-11
CVE-2025-27256 GE Vernova EnerVista UR 访问控制错误漏洞 — EnerVista UR Setup 8.3 High 2025-03-10
CVE-2025-24924 GMOD Apollo Missing Authentication for Critical Function — Apollo 9.8 Critical 2025-03-05
CVE-2025-21355 Microsoft Bing Remote Code Execution Vulnerability — Microsoft Bing 8.6 High 2025-02-19
CVE-2025-25224 LuxSoft LuxCal Web Calendar 访问控制错误漏洞 — The LuxCal Web Calendar 7.5 - 2025-02-18
CVE-2025-24865 mySCADA myPRO Manager Missing Authentication for Critical Function — myPRO Manager 10.0 Critical 2025-02-13
CVE-2025-0896 Orthanc Server Missing Authentication for Critical Function — Orthanc server 9.8 Critical 2025-02-13
CVE-2025-0108 PAN-OS: Authentication Bypass in the Management Web Interface — Cloud NGFW 9.8 - 2025-02-12
CVE-2025-26366 Q-Free MAXTIME Suite 访问控制错误漏洞 — MaxTime 7.5 High 2025-02-12
CVE-2025-26365 Q-Free MAXTIME Suite 访问控制错误漏洞 — MaxTime 7.5 High 2025-02-12
CVE-2025-26364 Q-Free MAXTIME Suite 访问控制错误漏洞 — MaxTime 7.5 High 2025-02-12
CVE-2025-26363 Q-Free MAXTIME Suite 访问控制错误漏洞 — MaxTime 7.5 High 2025-02-12
CVE-2025-26362 Q-Free MAXTIME Suite 访问控制错误漏洞 — MaxTime 7.5 High 2025-02-12
CVE-2025-26361 Q-Free MAXTIME Suite 访问控制错误漏洞 — MaxTime 9.1 Critical 2025-02-12
CVE-2025-26360 Q-Free MAXTIME Suite 访问控制错误漏洞 — MaxTime 5.3 Medium 2025-02-12
CVE-2025-26359 Q-Free MAXTIME Suite 访问控制错误漏洞 — MaxTime 9.8 Critical 2025-02-12
CVE-2025-26347 Q-Free MAXTIME Suite 访问控制错误漏洞 — MaxTime 9.8 Critical 2025-02-12
CVE-2025-26345 Q-Free MAXTIME Suite 访问控制错误漏洞 — MaxTime 9.8 Critical 2025-02-12
CVE-2025-26344 Q-Free MAXTIME Suite 访问控制错误漏洞 — MaxTime 9.8 Critical 2025-02-12
CVE-2025-26342 Q-Free MAXTIME Suite 访问控制错误漏洞 — MaxTime 9.8 Critical 2025-02-12
CVE-2025-26341 Q-Free MAXTIME Suite 访问控制错误漏洞 — MaxTime 9.8 Critical 2025-02-12
CVE-2025-26339 Q-Free MAXTIME Suite 访问控制错误漏洞 — MaxTime 9.8 Critical 2025-02-12
CVE-2025-21198 Microsoft High Performance Compute (HPC) Pack Remote Code Execution Vulnerability — Microsoft HPC Pack 2016 9.0 Critical 2025-02-11
CVE-2024-10649 Unauthenticated File Upload in wandb/openui — wandb/openui 10.0 - 2025-02-10
CVE-2024-54176 IBM UrbanCode Deploy missing authentication — UrbanCode Deploy 4.3 Medium 2025-02-08
CVE-2024-12511 SMB/FTP Address Book Scan Pass-back attack — Versalink B400 7.6 High 2025-02-03
CVE-2024-12957 ASUS Armoury Crate Service 访问控制错误漏洞 — Armoury Crate 8.1 - 2025-01-23
CVE-2024-12757 Nedap Librix Ecoreader Missing Authentication for Critical Function — Ecoreader 8.6 High 2025-01-17
CVE-2025-0456 NetVision Information airPASS - Missing Authentication — airPASS 9.8 Critical 2025-01-16

Vulnerabilities classified as CWE-306 (关键功能的认证机制缺失) represent 1920 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.