282

Port 282/tcp is registered with IANA under the service name cableport-ax, described as "Cable Port A/X," with assignee Craig Langfahl and a blank Reference field. The registry carries dual entries for both TCP and UDP that are otherwise identical apart from the transport column, confirming the assignment covers both transports rather than being TCP-specific. Beyond the bare IANA registration, no primary source — vendor documentation, RFC, or software manual — describes what actually implements or listens on this port. The service name itself suggests some link to cable-modem or headend "Port A/X" management hardware from the individual-registrant era of the IANA registry (the assignee is a person, not a company or standards body), but this is inference from the name alone, not a sourced fact, so it is flagged as unknown rather than asserted. The port does not appear in Wikipedia's List of TCP and UDP port numbers (which jumps from 280 to 300), and a search for CVEs, malware, botnets, or scanning writeups tied to either "port 282" or "cableport-ax" turned up nothing. The one cable-modem-adjacent exploit surfaced during research, Cable Haunt (disclosed January 2020), targets an unrelated port (8080, the modem's local management interface) and is unrelated to this registration — noted here only to rule it out, not to imply any connection. Given the thin evidentiary base, this entry should publish the confirmed IANA facts plainly and avoid asserting software, exploit history, or scanning prevalence that no source supports.

IANA assignment

cableport-ax — "Cable Port A/X"; reference (blank — no RFC cited in IANA registry); assignee Craig Langfahl; dual-registered 282/tcp + 282/udp [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml (cached CSV, lines 612-613)

Range class

well-known (0–1023) [Confirmed]

Prevalence

no nmap-services frequency or scanning-prevalence data located in this pass [Unknown]

Related ports

none identified

Primary use

Unknown beyond the IANA label. Plausibly a legacy, vendor-registered name tied to older cable-modem/headend management tooling (individual-registrant pattern), but no primary source documents an actual wire protocol, client, or server using this port

Other/unofficial uses

none found in this pass [Unknown]

Security implications

no CVEs, malware families, botnets, or scanning/threat-intel writeups reference port 282 or "cableport-ax"; explicitly distinct from Cable Haunt, which targets an unrelated port (8080) on cable-modem local-management interfaces [Confirmed absence of hits in searched sources] — https://cablehaunt.com/, https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers

Typically seen on

Unknown — no deployment evidence found

Analyst note

thin factual base; publish only the IANA-sourced service name, description, transport, and assignee. Do not assert a specific product, exploit history, or scanning prevalence — none is sourced.

Port 282 is registered with IANA under the service name cableport-ax, described simply as "Cable Port A/X," with Craig Langfahl listed as both assignee and contact (the IANA Service Name and Transport Protocol Port Number Registry, row 613; corroborated at iana.org). The registration carries no RFC or other IANA reference, and both the registration-date and modification-date fields are blank — a common pattern among older Service Name and Transport Protocol Port Number Registry entries recorded before IANA began populating those columns, not a data-collection gap. An identical entry exists for 282/tcp (row 612), so the assignment is dual-registered across both transports under the same name and owner. Beyond the bare registry listing, no authoritative protocol specification, vendor implementation guide, or wire-format document could be located; the name suggests some tie to cable-modem provisioning or management hardware ("Cable Port"), plausibly an IBM "A/X" product line, but this link is unverified and not asserted as fact. Cisco's NBAR protocol library appears to list cableport-ax by name in its protocol pack documentation, but the source PDF returned an HTTP 403 and could not be fully retrieved to confirm details. No honeypot, Shodan/Censys, or SANS ISC exposure data exists for this port, and no malware family has been publicly tied to it — an open 282/udp today would be unusual and would warrant investigation on its own merits rather than against a known threat signature.

IANA assignment

cableport-ax — "Cable Port A/X"; reference blank (no RFC cited in registry); assignee/contact [Craig_Langfahl]; dual-registered 282/tcp + 282/udp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry (corroborated: https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?page=6)

Range class

well-known (0–1023) [Confirmed]

Registration date / modification date

both blank in the registry — left blank, not fabricated [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry

Prevalence / exposure

nmap-services observed open-frequency 282/udp ≈ 0.000494 (very low — roughly 5 in 10,000 scanned hosts in the nmap-services sample) [Confirmed] — nmap-services dataset; the dual-registered 282/tcp row records 0.000000 in the same dataset [Confirmed] — nmap-services dataset. Beyond that figure, no honeypot, Shodan/Censys, or SANS ISC telemetry was found; one low-credibility templated port-info page states no known trojan/virus association, unverifiable

[Unknown] — https://www.auditmypc.com/udp-port-282.asp

Related ports

282/tcp (identical dual registration, same name/description/assignee) [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry

Primary use

Unknown — no protocol specification, wire-format document, or vendor implementation guide found beyond the bare IANA name/description [Unknown]

Other/unofficial uses

cableport-ax appears by name in Cisco NBAR protocol library documentation, but the source PDF returned HTTP 403 and full content could not be confirmed [Likely] — https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/qos_nbar/prot_lib/config_library/pp1200/nbar-prot-pack1200/nbar-prot-c1200.pdf

Security implications

Unknown — no malware association or scanning telemetry located in public sources [Unknown]

Typically seen on

Unknown — no identified live implementation or product found [Unknown]