Back to Labs
Weakness (CWE)

CWE-306

Missing Authentication for Critical Function

About

The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Common consequences

  • Access Control, Other → Gain Privileges or Assume Identity, Varies by Context

Mitigations

  • 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
  • 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
  • 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 separati
  • 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].

CVEs with this weakness

Frequently asked questions

What is CWE-306?

The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. Common consequences Access Control, Other → Gain Privileges or Assume Identity, Varies by Context Mitigations Architecture and Design: Divide the software into anonymous, normal, privileged, and administrative areas.

How likely is CWE-306 to be exploited?

MITRE rates the likelihood of exploit for CWE-306 as high.

Which platforms does CWE-306 affect?

CWE-306 has been observed on: Cloud Computing, ICS/OT.

How many CVEs does Rainforest track for CWE-306?

Rainforest Labs currently tracks 2 published CVEs mapped to CWE-306. They are listed on this page.

Empower Your Security Strategy with Rainforest

Discover vulnerabilities early, prioritize critical threats, and protect what truly matters. Rainforest streamlines your security operations, saving you time and reducing costs, so you can focus on what drives your business forward.