The Redis instance is open to the public.
This could result to data leak and code execution.
Severity: medium
Fingerprint: d606b92f1b5fdf1897c596ab97c596ab97c596ab97c596ab97c596ab97c596ab
Redis is open with 4 keys in dbs
Severity: medium
Fingerprint: d606b92f1b5fdf18476e4752476e4752476e4752476e4752476e4752476e4752
Redis is open with 1 keys in dbs
Severity: medium
Fingerprint: d606b92f1b5fdf180bb9df7e0bb9df7e0bb9df7e0bb9df7e0bb9df7e0bb9df7e
Redis is open with 5 keys in dbs
Severity: medium
Fingerprint: d606b92f1b5fdf18253c1e95253c1e95253c1e95253c1e95253c1e95253c1e95
Redis is open with 6 keys in dbs
Severity: medium
Fingerprint: d606b92f1b5fdf185732408f5732408f5732408f5732408f5732408f5732408f
Redis is open with 0 keys in dbs
The Kafka instance is available to the public without authentication.
An attacker could connect to the queue to extract private/confidential information in real-time.
Fingerprint: 43224224eeda9da960defeaa20adb0e51c304c151c304c151c304c151c304c15
NoAuth Found topic first Found topic __consumer_offsets