Skip to content
AdminKit

Is port 554 (RTSP) exposed to the internet, and how do I lock it down?

AdminKit explains why port 554, RTSP's default port, is a common camera-exposure finding: RTSP streams live video from IP cameras, NVRs and doorbells but has no built-in authentication or encryption, so a camera reachable on port 554 without a separately configured username and password can let anyone with the right URL watch the feed.

By AdminKit team, Netbase JSC · Updated

Key takeaways

  • Port 554 is RTSP’s registered port. IP cameras, NVRs, DVRs, video doorbells and encoders use it to let viewers and recorders pull a live stream.
  • RTSP borrows HTTP’s login schemes but doesn’t require one. The RTSP 2.0 standard says Basic credentials must only travel over TLS, yet most cameras serve plain RTSP on 554.
  • An exposed 554 gives away more than video: stream details, a request that can point a stream at someone else, and the camera’s RTSP server code to anyone who connects.
  • AdminKit’s RTSP check sends only OPTIONS and DESCRIBE, without credentials, to your own IP and tells you whether the stream description comes back without a login.

Why is port 554 open on so many cameras?

RTSP (RFC 7826) is a control protocol, not an encryption standard — it negotiates and manages a media stream between a client (a viewing app or NVR) and a camera, and by default that negotiation and the resulting video stream are both unauthenticated and unencrypted. Camera manufacturers ship RTSP enabled out of the box because it’s the simplest way to let any third-party viewing app or recorder pull the feed, and many deployments never add the vendor’s optional authentication layer on top.

Many devices speak RTSP 1.0, defined in RFC 2326 in 1998, even though RFC 7826 (RTSP 2.0, 2016) obsoletes it; AdminKit’s RTSP check sends RTSP/1.0 requests. Both versions use port 554 by default, and RFC 7826 lists the registered ports: “554 (rtsp) and 322 (rtsps)”, plus an alternative registered port, 8554. So a camera found on 8554 is the same exposure as one on 554, and the encrypted rtsps port, 322, is the one that carries RTSP over TLS.

How does RTSP decide who may watch?

RTSP reuses HTTP authentication. RFC 7826’s security framework says RTSP and HTTP “share common authentication schemes”, that servers “SHOULD implement both the Basic and the Digest authentication schemes”, and that a server asks for credentials with a 401 and a WWW-Authenticate header. Two sentences from that section matter most for an exposed port:

  • “Using the HTTP authentication alone does not provide full RTSP message security. Therefore, TLS SHOULD be used.”
  • “Any RTSP message containing an Authorization header using the Basic authentication scheme MUST be using a TLS connection.”

Put next to how cameras are actually deployed, that gives three common states:

Camera settingWho can view over an exposed port 554What else leaks
No stream authenticationAnyone who knows or guesses the stream pathEverything: stream, details, and the camera’s RTSP code
Basic authentication on plain RTSPAnyone with the password, and anyone who captures it on the way, since Basic credentials are only encoded, not encryptedThe video itself, which is not encrypted either
Digest authentication on plain RTSPAnyone with the password; the password itself is not sent in the clearThe video, if someone on the path captures it

None of the three makes an internet-facing port 554 a good idea. Digest is the best of them, and it still leaves the video and the camera’s request parser open to the internet.

What can someone do with an exposed port 554?

At minimum, an exposed RTSP stream means unauthorized viewing of whatever the camera sees — a real privacy problem for a home, office, or retail camera. In 2014, the website Insecam drew wide media coverage (WeLiveSecurity, CBS News, TechCrunch) by indexing roughly 73,000 cameras worldwide that were reachable with unchanged default passwords, most delivering their feed over RTSP or a similarly unauthenticated stream — a stark public demonstration of how common this exposure pattern is.

The RTSP methods themselves give a stranger more than a picture:

RTSP requestWhat it returns or doesWhy it matters on an exposed camera
OPTIONSThe list of methods the server supportsConfirms an RTSP server and hints at its software
DESCRIBEA session description (SDP): codecs, resolution, track URLs, sometimes a device or session nameTells a viewer exactly how to set up the stream
SETUP and PLAYStarts media deliveryThe live feed itself
SETUP naming another destinationAsks the server to send media to a different addressRFC 2326 warns this allows a “remote-controlled denial-of-service attack” unless the server has verified the client

RFC 2326’s own advice for that last row is that a server “SHOULD only allow client-specified destinations for RTSP-initiated traffic flows if the server has verified the client’s identity”. A camera with no stream authentication has verified no one.

Then there is the server code. Some RTSP server implementations have had separate authentication-bypass or buffer-overflow vulnerabilities over the years, meaning an exposed stream can occasionally be a foothold into the device itself, not just a video feed. One documented example: CVE-2018-4013 describes an “exploitable code execution vulnerability” in the HTTP packet-parsing of the LIVE555 RTSP server library version 0.92, triggered by “a specially crafted packet”. Whether a given camera is affected depends on its firmware, which is the point: with 554 open, the internet gets to find out before you do.

How do you check your own exposure?

Confirm your public IP with what is my IP, then AdminKit’s open ports check tests whether port 554, alongside other commonly-exposed device ports, responds from outside your own network — only ever against the IP making the request, with consent. AdminKit’s dedicated RTSP exposure check goes further: it reads back whether the camera’s stream description is viewable without authentication, not just whether the port is open.

The RTSP check is deliberately narrow. It connects to your own public IP on 554 (or a port you enter, if you forwarded a different one), sends an RTSP/1.0 OPTIONS and then a DESCRIBE for the path /, and stops. It never sends credentials, and it never sends SETUP or PLAY, so it never pulls video. Read the result like this:

State shownWhat happenedWhat it means
Stream description exposedDESCRIBE returned 200 with an SDP body (an excerpt is shown)Anyone on the internet can set up this stream. Remove the forward today
Authentication requiredDESCRIBE returned 401 or 403; the WWW-Authenticate scheme is shownA login is enforced at /. If the scheme is Basic, the password crosses the internet readable
No default stream exposedAny other answer, such as 404Nothing is served at /. Many cameras publish streams at vendor paths like /stream1, so this is not proof the real stream is protected
Could not reach the serverNo RTSP answer on that portNot reachable from the internet on this IP and port

On the port check, an open 554 appears as “554 (RTSP) Open” with a high-severity finding, “RTSP — camera/media stream, often unauthenticated”. Either result is your cue to find the device.

How do you find which camera is answering?

Start at the router: look for a port forward or UPnP mapping for TCP 554, 8554, or whatever port the RTSP check used, and note the internal address it points to. Then, from a machine on your own LAN, ask that address which RTSP methods it supports with Nmap’s rtsp-methods script. The output below is the format shown in the script’s documentation, with a private example address:

$ nmap -p 554 --script rtsp-methods 192.168.1.30
PORT    STATE SERVICE
554/tcp open  rtsp
| rtsp-methods:
|_  DESCRIBE, SETUP, PLAY, TEARDOWN, OPTIONS

Match the address to a device in your router’s client list or the NVR’s camera list. If the forward points at the NVR rather than a camera, every camera the NVR proxies is in scope. To test whether the camera’s real stream path asks for a login, use the curl --rtsp-request DESCRIBE test in Telnet and RTSP camera/router exposure. Cameras with port 554 forwarded often have their web interface forwarded too, and camera web servers are a known target: CISA’s Known Exploited Vulnerabilities catalog lists, for example, CVE-2021-36260 in Hikvision cameras’ web server. Check both ports while you are at it.

How do you lock port 554 down?

  • Change the camera’s default admin credentials — this is the single step that stops both casual scanning and tools like Insecam from working.
  • Turn on the camera’s built-in RTSP authentication if it offers one; many budget cameras ship it disabled by default even though the firmware supports it. Choose Digest over Basic if the camera lets you pick.
  • Remove any port-forward or UPnP rule exposing 554 (or 8554) directly to the internet; if you need to view the feed remotely, use the vendor’s cloud app or a VPN into your own network instead of forwarding the raw stream port.
  • Update the camera and recorder firmware, since the RTSP server code is part of it.
  • Re-run open ports check and the RTSP exposure check to confirm 554 is no longer reachable from outside.

See Telnet and RTSP camera/router exposure for the full walkthrough, including the closely related Telnet (port 23) exposure that shows up on the same hardware and a safer camera network layout. Reference: RTSP.

Which cameras may you test?

Every check this page links to is for assets you own or are explicitly authorized to test. Never scan, probe, or attempt to connect to a network or device you don’t control — AdminKit’s active checks only ever run against the IP making the request or an asset you’ve verified ownership of. See our Disclaimer and Acceptable Use Policy for the full terms.

This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.

Frequently asked questions

Is RTSP itself insecure, or just how it's usually deployed?

RTSP (RFC 7826) is a streaming control protocol, not an encryption standard — it negotiates a media stream, and by default that stream and its control channel are unauthenticated. The insecurity comes from devices exposing it directly to the internet with default or no credentials, not from a flaw unique to RTSP itself.

What can someone actually see or do with an exposed RTSP stream?

At minimum, unauthorized live viewing — the exact exposure the Insecam website's 2014 camera index demonstrated at scale. Some RTSP server implementations have also had separate authentication-bypass or buffer-overflow vulnerabilities, so an exposed stream can occasionally be a foothold into the device itself, not just a video feed.

Is 554 always RTSP?

554 is IANA's registered RTSP port, but confirm what's actually listening rather than assuming — a port scan alone doesn't identify the protocol behind it.

What's the single most effective fix?

Changing the camera's default admin credentials — that one step defeats both casual scanning and tools built specifically to find devices with unchanged defaults.

Does a password on the stream make port 554 safe to forward?

Not on its own. On plain RTSP the video still travels unencrypted, and RFC 7826 says Basic authentication must only be sent over TLS. A camera that accepts Basic credentials on port 554 sends them readable to anyone on the path. Keep 554 off the internet and view remotely through a VPN or the recorder.

Want AdminKit to watch this for you?

Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.

Huy Nguyen (David), Founder and CEO of Netbase JSC

Talk to an expert

Huy Nguyen (David), Founder & CEO, Netbase JSC

Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.