whatportis.com
suggest an edit →

Port 2948WAP Push MMS

Port 2948 handles WAP Push Multimedia Messaging Service (MMS) communications over both TCP and UDP. It is primarily associated with delivering multimedia content to mobile devices in cellular networks. This port facilitates the transmission of rich MMS messages — including images, videos, and audio — by leveraging Wireless Application Protocol (WAP) push mechanisms..

inNetwork ServicesCloudMobile
transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
2/10

safe

lookups
11,708

rank 340 of 993 · top 34%

Technical Details

what runs on :2948

WAP Push Multimedia Messaging Service (MMS) running over port 2948 was designed to facilitate the delivery of rich multimedia content across mobile networks. It uses the Wireless Application Protocol (WAP), which defines standards for Internet communication over wireless cellular networks, optimized for devices with limited bandwidth and resources.

Technically, WAP Push enables content providers to send service indication or service loading messages to devices, triggering actions such as fetching an MMS from an MMS center (MMSC). The mechanism typically involves sending a specially formatted push message that includes a URL pointing to the multimedia content. When received, the mobile device processes the push message, prompts the user, or automatically retrieves the accompanying MMS based on configuration and user preferences.

Port 2948 handles WAP Push over both UDP and TCP, balancing quick delivery (via UDP) with the need for reliable acknowledgments (via TCP) in certain contexts. While once widely used, especially on 2G/3G networks during the early mobile Internet era, modern LTE and 5G networks tend to use more evolved IP-based messaging protocols, reducing reliance on WAP.

Security Information

exposure of :2948

risk score

2/ 10safe

routine exposure. this port is rarely the way in on its own — keep it patched and logged and move on.

network services averages 3.9 across 604 ports — this one sits 1.9 below.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

Common Vulnerabilities:

  • Spoofing and phishing attacks: Malicious push messages can be crafted to deceive users into clicking harmful links, potentially exposing personal data.
  • Denial of Service: Mass unsolicited push messages can overwhelm devices or cause service interruptions.
  • Message interception: Without encryption, WAP Push data can be intercepted over untrusted or compromised networks, risking privacy breaches.

Common Mitigations:

  • Authentication: Ensuring the MMS push originates from trusted, authenticated sources to prevent spoofing.
  • Filtering: Carrier gateways and devices should filter or sandbox push content to restrict malicious payloads.
  • User consent: Devices can prompt users before fetching or opening MMS content received via push.
  • Migration: Transitioning to more secure, encrypted protocols such as HTTPS-based messaging services.
  • Network segmentation: Limiting port exposure on public-facing network interfaces to reduce attack surfaces.

Related Ports

all 604 in network services →

the 8 most looked-up other ports in network services — 604 ports carry that label.

portservicerisk
:9080Groove RPCcaution
:6543Jetnetcaution
:5938TeamViewercaution
:8291Winbox MikroTik Admincaution
:3233WhiskerControl Protocolcaution
:3268Microsoft Global Catalog (GC)caution
:135Microsoft EPMAPcaution
:3128Tatsoft Default HTTP Proxycaution

risk mix of the 8 listed

  • caution100%

0 of 8 encrypted