Skip to main content

Lack of isolation methods

Description

The system do not use isolation methods for running applications.

Impact

Allow the construction of covert communication channel.

Recommendation

  • Use dedicated cloud servers rather than VMs or cloud-based containers.
  • Implement specific isolation strategies, particularly between hosts and the network.

Threat

External attacker with access to the application.

Expected Remediation Time

⌚ 120 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: H
  • Integrity: L
  • 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:H/I:L/A:N/E:X/RL:X/RC:X
  • Score:
    • Base: 8.2
    • Temporal: 8.2
  • Severity:
    • Base: High
    • Temporal: High

Code Examples

Compliant code

The networks are correctly separated using VLAN permissions

name: yournetwork
dns_domain: 208.67.222.222
subnets:
subnet_name_a:
ip_subnet: 192.0.2.0/24
allocation_pools:
- start: 192.0.2.50
end: 192.0.2.99
gateway_ip: 192.0.2.1
vlan: 102
subnet_name_b:
ip_subnet: 198.51.100.0/24
allocation_pools:
- start: 198.51.100.50
end: 198.51.100.99
gateway_ip: 198.51.100.1
vlan: 101

Non compliant code

There are no network isolation methods configured, so an attack in one of the networks could potentially affect all others

name: yournetwork
dns_domain: 192.0.2.0/24
subnets:
subnet_name_a:
ip_subnet: 192.0.2.0/24
allocation_pools:
- start: 0.0.0.0
end: 255.255.255.255
gateway_ip: 192.0.2.1

Requirements