Skip to main content

Business information leak - Redis

Description

Due to a misconfiguration of the Redis service, it is possible to connect to the dictionary server and obtain business information by deserializing objects contained in the keys, from which the following can be extracted:

  • List of users.
  • Employee information such as IDs and names.
  • Customer information such as Nits, names and IDs.

Impact

Obtain information from users, customers and employees.

Recommendation

According to the classification of the information found, establish the necessary controls so that the information is accessible only to the indicated persons and from authorized segments.

Threat

Internal attacker with Redis credentials.

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: A
  • Attack complexity: L
  • Privileges required: H
  • User interaction: N
  • Scope: U
  • Confidentiality: H
  • Integrity: N
  • Availability: N

Temporal

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

Result

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

Code Examples

Compliant code

Servers with sensitive information have protected modes enabled

serverConfiguration:
bind * -::*
enable-protected-configs no
enable-debug-command no
tls-port 6379
tls-key-file redis.key
tls-auth-clients no
tls-protocols "TLSv1.2 TLSv1.3"
tls-ciphersuites TLS_CHACHA20_POLY1305_SHA256
protected-mode yes

Non compliant code

The server configuration does not enable protected mode

serverConfiguration:
bind * -::*
enable-protected-configs no
enable-debug-command no
tls-port 6379
tls-key-file redis.key
tls-auth-clients no
tls-protocols "TLSv1.2 TLSv1.3"
tls-ciphersuites TLS_CHACHA20_POLY1305_SHA256
protected-mode no

Requirements