Skip to content
AdminKit

Is port 7547 (TR-069) exposed beyond your ISP's management network?

Port 7547 runs TR-069 (CWMP), the protocol many ISPs use to remotely configure the router they gave you — a legitimate management channel, but in November 2016 a Mirai botnet variant used a flaw in how some routers handled a command over this port to knock roughly 900,000 Deutsche Telekom customers offline in a weekend. AdminKit explains the risk.

By AdminKit team, Netbase JSC · Updated

Key takeaways

  • Port 7547 is the IANA port for CWMP, the protocol behind TR-069. On many ISP routers it is the “Connection Request” listener the ISP uses to ask the router to call home.
  • The specification is strict about that listener: one purpose only, a per-device random URL path, Digest authentication and an empty reply. Anything else answering on 7547 is outside the spec.
  • In 2016, routers that also answered a TR-064 command on 7547 were hit by a Mirai variant. The flaw on one model is recorded as CVE-2016-10372.
  • AdminKit’s port check tests 7547 on your own public IP. “Open” means anyone on the internet reaches the listener; ask your ISP to filter it to their own servers.

What’s running on 7547, and why?

TR-069 (Technical Report 069, the specification that defines CWMP — the CPE WAN Management Protocol) lets an ISP’s Auto-Configuration Server push firmware updates, change settings and diagnose problems on the router or modem they provided, without a technician visit. It’s a normal, widely deployed management tool — the question isn’t whether TR-069 exists, but whether port 7547 is reachable from anywhere beyond your ISP’s own management network.

What listens on 7547 is usually the ISP-supplied gateway: a DSL, cable or fibre modem-router, or an optical network terminal with routing built in. Other customer equipment managed the same way, such as VoIP adapters and set-top boxes, can run a CWMP client too. A router you bought and installed yourself rarely has a reason to listen on 7547, because no ISP is managing it. IANA registers 7547 for CWMP on UDP as well as TCP. In the specification, UDP 7547 is the default destination on the ACS side for the router’s lightweight notifications, so that use of the UDP port is traffic from your router toward the ISP’s servers. AdminKit’s check tests the TCP listener. How the listener fits into the full TR-069 session flow is explained in TR-069/CWMP: why ISPs use it and when it’s a risk.

What should a TR-069 listener on 7547 look like?

The Broadband Forum’s TR-069 specification (Amendment 6 Corrigendum 1, section 3.2.2) sets out the rules for the Connection Request listener. They are worth knowing, because they describe what a safe answer on 7547 looks like and make deviations easy to spot:

Specification requirementWhat it means for an exposed port 7547
The port “MUST only be used for TR-069 connection requests. It MUST NOT be shared with any other protocol.”A web page, login form or other service on 7547 is outside the spec
The request is “an HTTP 1.1 GET to a specific URL designated by the CPE”, whose path “SHOULD be randomly generated by the CPE so that it is unique per CPE”A guessable path, or one that answers at /, gives scanners an easier target
The CPE “MUST use HTTP authentication with the HTTP Digest Authentication scheme” before actingAn unauthenticated request should get a Digest challenge and nothing else
A successful request gets “200 (OK)” or “204 (No Content)”, and the response body “MUST be zero” lengthContent in the body of a reply is outside the spec
The CPE “SHOULD restrict the number of Connection Requests” and answers excess ones with HTTP 503Rate limiting is expected, to reduce denial of service

Two details stand out. First, the specification says the Connection Request “MUST make use of HTTP, not HTTPS”, so the listener is a plaintext HTTP server by design; its safety rests on the Digest check and on the code that parses requests. Second, the listener itself carries no commands, as “no data is conveyed in the Connection Request HTTP GET”. The router responds by calling its configured ACS, so a correct implementation gives an outsider nothing to work with beyond the parser itself.

What went wrong in 2016?

In November 2016, a Mirai botnet variant scanned the public internet for devices listening on port 7547 and sent a crafted command exploiting a flaw in how certain router models handled a related TR-064 request. Deutsche Telekom’s own routers weren’t vulnerable to the underlying code-injection, but the volume of malicious scan traffic alone crashed roughly 900,000 of them over a single weekend — widely reported at the time and later documented in the USENIX Security 2017 Mirai study. In the aftermath, affected ISPs restricted public access to port 7547 and pushed firmware patches.

Set against the specification above, the root cause is plain. TR-064 is a separate configuration protocol meant for the local network side, yet the vulnerable routers answered it on the same port as TR-069’s Connection Request, the one the spec says must not be shared. The National Vulnerability Database records one of the affected models as CVE-2016-10372: “The Eir D1000 modem does not properly restrict the TR-064 protocol, which allows remote attackers to execute arbitrary commands via TCP port 7547”, with the NewNTPServer feature as the injection point. A device following the single-purpose rule would not have exposed that command to the internet.

How do you check your own exposure?

AdminKit’s open ports check covers port 7547 — one of the nine TCP ports it scans on your own public IP — confirm your current public IP first with what is my IP, then run the check to see whether 7547 responds from outside your ISP’s network. If you manage your own hardware rather than relying on an ISP-provided router, this is worth checking directly, and if you’re responsible for more than one device, using the port-check tool to inventory IoT device exposure covers how to repeat this kind of check across a whole fleet of routers and other CPE rather than one at a time.

The check runs from AdminKit’s servers, which are not your ISP’s management servers. That is useful: if your ISP filters 7547 so only its own ACS can reach it, the check sees it as closed, which is the result you want.

How do you read the result for port 7547?

What the port check showsWhat it meansWhat to do
“7547 (TR-069) Open”, with a high-severity finding “TR-069 (CWMP) — ISP device management, frequent exploit target”Anyone on the internet can open a TCP connection to the listener on this IPAsk your ISP to filter 7547 to its management servers; keep firmware updates on
“7547 (TR-069) Closed/filtered”No TCP connection completed within the check’s timeoutThe ISP filters the port, or nothing listens; re-check after a router swap or firmware update
7547 open on a router you installed yourselfYour own router, or a device it forwards to, is listening on 7547Find out why; your own router has no ISP to answer to
7547 open while your line uses carrier-grade NATThe public IP is shared, so the listener may be carrier equipment, not yoursSee what is CGNAT before acting on the result

The finding’s fix hint, “Close this port, or restrict it to a VPN/allowlist if it must stay open”, translates to “ask the ISP for an allowlist” on ISP equipment. For a one-request test of what answers on an open 7547, the curl check in the full TR-069 guide shows what a Digest challenge looks like. Compare what you see with the specification table above.

How do you confirm the listener on your own equipment?

On an ISP-supplied router, you usually can’t see the CWMP settings. Some admin pages show a “TR-069”, “ACS” or “remote management” section with the ACS address; that confirms the client is configured, but you usually can’t change it.

On a router you control, such as one running Linux or OpenWrt, check the router itself for a process bound to 7547. The output below is an illustrative example:

$ ss -tlnp | grep 7547
LISTEN 0  5  0.0.0.0:7547  0.0.0.0:*  users:(("cwmp-client",pid=1402,fd=6))

No output means nothing on the router listens there. In that case an open 7547 in the outside check comes from a forward to a device behind it, or from an ISP device in front of it, so check the forward list and whether the ISP box is in bridge mode.

What should you do if it’s reachable?

On most ISP-provided routers, TR-069 access is configured by the ISP, not something you can toggle from the device’s own admin page — if port 7547 appears reachable from the broader internet rather than just your ISP’s management network, contact your ISP to ask whether access is properly restricted. If you’ve replaced the ISP router with your own hardware, make sure nothing on it is listening on 7547 at all, since you have no legitimate reason to run a CWMP management endpoint without an ISP operating it.

See our full guide, TR-069/CWMP: why ISPs use it and when it’s a risk, for more on how the 2016 incident unfolded and the options for putting your own router behind the ISP device.

Which devices 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

Does having TR-069 enabled automatically mean I'm at risk?

No — a well-implemented ACS connection restricted to your ISP's own management network is normal and reasonable. The 2016 incident happened because specific router models mishandled a related command insecurely, and the port was reachable more broadly than it should have been.

What actually happened in the 2016 incident?

A Mirai variant scanned for port 7547 and sent a crafted TR-064 command; Deutsche Telekom's specific routers weren't vulnerable to the underlying code-injection itself, but the volume of malicious scan traffic crashed roughly 900,000 of them anyway.

Can I turn TR-069 off myself?

Usually not on an ISP-provided router — it's typically configured by the ISP and isn't an exposed setting on the router's own admin page. If you're concerned, ask your ISP whether access is restricted to their management network.

Did ISPs fix this after 2016?

Affected ISPs restricted public access to port 7547 and pushed firmware patches, and filtering the port so only the ISP's own servers can reach it is the usual fix. Whether your own line is filtered is something to check rather than assume, which is what the port check on this page does.

What should normally answer on port 7547?

Only TR-069's Connection Request handler. The Broadband Forum specification says that port must be used only for connection requests and must not be shared with any other protocol. A login page, a SOAP service or any other content on 7547 is a sign the device is doing more on that port than the specification allows.

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.