Skip to main content

Authentication mechanism absence or evasion

Description

The system lacks an authentication mechanism or has one that can be bypassed. Therefore, an attacker can access resources that should be protected without having an active session.

Impact

Bypass the login mechanism a nd get unauthorized access to the application

Recommendation

Each criticial functionality resource for the organization must have a strong authentication process and it needs to be assured that each user trying to access has an initialized session.

Threat

Anonymous attacker from the Internet.

Expected Remediation Time

⌚ 60 minutes.

Score

Default score using CVSS 3.1. It may change depending on the context of the vulnerability.

Base

  • Attack vector: N
  • Attack complexity: L
  • Privileges required: N
  • User interaction: N
  • Scope: U
  • Confidentiality: L
  • Integrity: N
  • Availability: N

Temporal

  • Exploit code madurity: X
  • Remediation level: X
  • Report confidence: X

Result

  • Vector string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:X/RL:X/RC:X
  • Score:
    • Base: 5.3
    • Temporal: 5.3
  • Severity:
    • Base: Medium
    • Temporal: Medium

Code Examples

Compliant code

Specify iam policies according to the strictest access requirements

resource "aws_iam_policy" "policy" {
name = "test_policy"
path = "/mypath"
description = "My test policy"

policy = jsonencode({
Version = "2012-10-17"
Statement = [
{
Action = [
"ec2:Describe*",
]
Effect = "Allow"
Resource = "db_critical"
},
]
})
}

Non compliant code

No authentication restrictions provided for a given cloud resource

provider "aws" {
region = "us-west-2"
access_key = "*"
}

Requirements