S4E just found a high-severity finding from [ai] pa ssl inspection control
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
low·Information Scans·Updated Dec 16, 2023

Murmur Service Mumble Voice Communication Client Scanner

Murmur Service Mumble Voice Communication Client Scanner

Est. Time~15 seconds
Scan TypeSingle Scan
Targetsdomain, ipv4, subdomain
CostFree
2.8k
Times Used
continuous scan runs
6.2k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
Detail

Detects the Murmur service (server for the Mumble voice communication client) versions 1.2.X.

The Murmur server listens on a TCP (control) and a UDP (voice) port with the same port number. This script activates on both a TCP and UDP port version scan. In both cases probe data is sent only to the UDP port because it allows for a simple and informative ping command.

The single probe will report on the server version, current user count, maximum users allowed on the server, and bandwidth used for voice communication. It is used by the Mumble client to ping known Murmur servers.

The IP address from which service detection is being ran will most likely be temporarily banned by the target Murmur server due to multiple incorrect handshakes (Nmap service probes). This ban makes identifying the service via TCP impossible in practice, but does not affect the UDP probe used by this script.

It is possible to get a corrupt user count (usually +1) when doing a TCP service scan due to previous service probe connections affecting the server.

Solution Advice

Only use components that do not have known vulnerabilities, only use components that when combined to not introduce a security vulnerability, and ensure that a misconfiguration does not cause any vulnerabilities.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.