|Publication number||US7701956 B2|
|Application number||US 11/363,978|
|Publication date||Apr 20, 2010|
|Filing date||Feb 28, 2006|
|Priority date||Feb 28, 2005|
|Also published as||US20060195611|
|Publication number||11363978, 363978, US 7701956 B2, US 7701956B2, US-B2-7701956, US7701956 B2, US7701956B2|
|Inventors||Jeffrey J. Howe|
|Original Assignee||Arris Group, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (8), Non-Patent Citations (2), Referenced by (12), Classifications (20), Legal Events (7)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application claims priority under 35 U.S.C. 119(e) to U.S. provisional patent application No. 60/657,156 entitled “Secure cable modem configuration file verification via a TFTP relay agent,” which was filed Feb. 28, 2005, and is incorporated herein by reference in its entirety.
This invention relates, generally, to communication networks and devices and, more particularly, to preventing unauthorized use of configuration file information.
Data-Over-Cable Service Interface Specifications (“DOCSIS”) has been established by cable television network operators to facilitate transporting data traffic, primarily internet traffic, over existing community antenna television (“CATV”) networks. In addition to transporting data traffic as well as television content signals over a CATV network, multiple services operators (“MSO”) also use their CATV network infrastructure for carrying voice, video on demand (“VoD”) and video conferencing traffic signals, among other types.
As with any providing of goods and/or services, the service of providing information over a broadband connection is unfortunately the target of fraud and theft. Since the providing of broadband services costs a certain amount, and the more bandwidth resources provided incurs an increasingly proportional amount of cost, unscrupulous users who subscribe to a certain amount of bandwidth resources often attempt to obtain a higher level of service without paying for it.
There are a number of methods by which theft of service occurs, including replaying a different, but valid, cable modem configuration file corresponding to higher service than the legitimate one associated with the subscriber's lower subscribed-to service level. Another method is for a hacker to generate a configuration file and use it to register the cable modem (“CM”). The hacker can generate a file if they discover the shared secret key that an MSO uses to generate a configuration file.
Thus, there is a need for a method and system for assuring that a cable modem downloads configuration information from the correct file on the correct server, and that the configuration information is not altered before a registration request is generated.
This is accomplished by relaying TFTP requests and responses between a cable modem and a TFTP server, while monitoring the contents of the configuration information. A relay agent at a relaying agent, typically a cable modem termination system (“CMTS”), appears to the cable modem as the TFTP server, and appears to the TFTP server as the cable modem. When a TFTP read request is received at the CMTS from the CM, a port number retrieved from a predetermined number of available ports is substituted for the port number of the CM. A check is performed at the CMTS to ensure that the requested configuration file name matches the file name in the DHCP packet, typically the DHCP ACK packet as known in the art, which has already been sent to the CM. If the file name matches, the relay agent forwards the TFTP read request packet from the CM to the TFTP server using the relay agent's address as the source address, the TFTP server's address as the destination address and the port number retrieved from the pool as the port number.
When data from the TFTP server destined for the CM is received at the relay agent, a determination is made whether a packet is the first packet of the TFTP data. If so, the source address/port pair are associated with the port number and the CM IP address/port pair that was previously associated with the port number retrieved from the pool. Then, this port number is returned to the pool for use by requests from other devices.
If the TFTP data packet is not the first packet of TFTP data, the source address and port are used to determine the address of the CM and the port number used by the CM. The TFTP source address and port numbers are replaced with the address of the relay agent/CMTS and the previously retrieved port number from the pool, respectively, and the destination address and port numbers are replaced with the address of the CM and the port number used by the CM determined from the source address/port pair originally in the packet.
Although the port number has been returned to the pool, the TFTP (source) address and port numbers are replaced with the address of the relay agent and the previously retrieved port number from the pool, respectively. This address/port number pair may be used to determine the address of the CM and the port number used by the CM when it sent the TFTP read request packet(s). These values corresponding to the source address and port numbers used in the TFTP read request are used by the relay agent as the destination address/port number for forwarding the TFTP data packets to the CM.
A TFTP acknowledgement packet received at the relay agent from the CM is modified at the relay agent by replacing the source address and port number with the destination address and port number, and by replacing the destination address and port number with the address of the server and the port number used by the server determined by looking up the server information associated with the source address/port pair originally in the packet. The modified TFTP acknowledgement packet is then forwarded to the TFTP server.
As a preliminary matter, it will be readily understood by those persons skilled in the art that the present invention is susceptible of broad utility and application. Many methods, embodiments and adaptations of the present invention other than those herein described, as well as many variations, modifications, and equivalent arrangements, will be apparent from or reasonably suggested by the present invention and the following description thereof, without departing from the substance or scope of the present invention.
Accordingly, while the present invention has been described herein in detail in relation to preferred embodiments, it is to be understood that this disclosure is only illustrative and exemplary of the present invention and is made merely for the purposes of providing a full and enabling disclosure of the invention. The following disclosure is not intended nor is to be construed to limit the present invention or otherwise to exclude any such other embodiments, adaptations, variations, modifications and equivalent arrangements, the present invention being limited only by the claims appended hereto and the equivalents thereof.
Method 100 starts at step 105 when a DHCP acknowledgement (“DHCP ACK”) packet is received at step 110 at the relay agent running on a CMTS. Instead of just forwarding the packet on to the cable, the relay agent at the CMTS intercepts the DHCP ACK and records at step 115 the address of the TFTP server (siaddr) from which the cable modem should request configuration information, the configuration file name contained in the packet and the address of the relaying agent gateway (giaddr). It will be appreciated that the address, giaddr, of the relay agent gateway is the address of the CMTS because the relay agent is running on the CMTS. After step 115, the relay agent overwrites the address of the TFTP server, siaddr, with giaddr at step 120. The packet is then forwarded to the cable modem at step 125 from the relay agent.
After receiving the DHCP ACK, the cable modem sends a TFTP read request packet toward the TFTP server. However, since the DHCP ACK was forwarded by the relay agent and the relay agent/CMTS address was substituted for the address of the TFTP server, the cable modem sends the TFTP request to the relay agent instead of directly to the TFTP server. The relay agent receives the TFTP read request packet from the cable modem at step 130.
At step 135, the relay agent associates the destination address (“DIP”), which is the address of the relay agent/CMTS, the source address (“SIP”) of the cable modem and the source port (“SPORT”) used by the cable modem with a transfer identifier. The transfer identifier is a port number retrieved from an available pool of port numbers. In the preferred embodiment, the pool comprises port numbers 6912 through 6943, which are registered ports that are currently unassigned by IANA, as known in the art.
At step 140, the relay agent determines whether the configuration file requested in the TFTP read request packet matches the file name recorded at step 115. If not, a filename mismatch message is stored at step 142 and the method advances to step 150.
If at step 140 a determination is made that the configuration file name in the TFTP request matches the name recorded at step 115, the process continues to step 150. At step 150, the relay agent overwrites the source address in the TFTP read request packet with the destination address contained therein, the destination address with siaddr (address of TFTP server) and the source port with the transfer identifier retrieved from the pool at step 135. The relay agent then forwards the TFTP read request packet according to the new destination address contained in the packet received at step 130, this new destination address being the stored siaddr.
Upon receiving the TFTP request packet from the relay agent, the TFTP server sends in reply TFTP data that may comprise more than one packet. The TFTP data packet(s) are sent to the relay agent because the source address of the packet modified at step 150 is the address of the relay agent rather than the cable modem. It will be appreciated that the data packets are sent one-at-a-time, waiting for an acknowledgement after each one.
The relay agent receives a TFTP data packet from the TFTP server at step 155. At step 160, the source address and port contained in the packet are associated with the transfer identifier, which is the destination port value in the TFTP data packet. Then, the transfer identifier is returned to the pool of available identifiers at step 165, so it may be used for other requests.
Because of the associations made at steps 135 and 160, the transfer identifier now may be used as a link between the CM address/port pair and the TFTP address/port pair. It will be appreciated that although the transfer identifier is returned to the pool, it may still be used for the current TFTP transaction and will not cause a conflict with other transactions because packets in each of those transactions is unique as defined by their respective CM and/or TFTP server address/port pair(s).
At step 167, the CM address and port are retrieved based on the transfer identifier. At step 173, the SIP and SPORT are replaced with the DIP and DPORT, respectively. Then, the DIP and DPORT are overwritten with the address and port of the CM at step 174. Type-length values are evaluated and recorded and possibly modified at step 180 before the packet is forwarded to the CM.
After receiving a TFTP data packet, a cable modem sends a packet back to the TFTP server acknowledging that it received same. After a TFTP acknowledgement packet is received from the cable modem at step 183, the TFTP server address and port are retrieved at step 185 based on the source address/port pair, which is the CM address/port pair. At step 190, the source port and address values are replaced with the destination port and address values, respectively. At step 195, the destination address and port values are overwritten with the TFTP server address and port values, respectively, and the acknowledgment packet is forwarded to the TFTP server.
A determination is made at step 197 whether a received data packet is the last TFTP data packet. If not, the process returns to step 170 and another TFTP data packet is received. The CM address and port values are retrieved at step 172 based on the SIP/SPORT pair, which is the TFTP server address/port pair, the CM address/port values being linked with the TFTP server address/port values by the transfer identifier as discussed above. The process continues to step 173 as discussed above.
If the determination at step 197 is yes, action is taken at step 198, when the CM sends a registration request. The action taken may be based on whether a filename mismatch message was recorded at step 142 and/or be based on the TLV data recorded at step 180. It will be appreciated that the MSO may decide to deny registration of the requesting cable modem at step 198. Alternatively, the MSO may decide to grant the registration request, but at a lower bandwidth, or quality of service (“QoS”). In addition, the MSO may decide to allow the requested registration at the requested QoS, but initiate a warning or message display that the cable modem has been granted an unauthorized level of QoS. The process ends at step 199.
These and many other objects and advantages will be readily apparent to one skilled in the art from the foregoing specification when read in conjunction with the appended drawings. It is to be understood that the embodiments herein illustrated are examples only, and that the scope of the invention is to be defined solely by the claims when accorded a full range of equivalents.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US6049826 *||Feb 4, 1998||Apr 11, 2000||3Com Corporation||Method and system for cable modem initialization using dynamic servers|
|US6070187 *||Mar 26, 1998||May 30, 2000||Hewlett-Packard Company||Method and apparatus for configuring a network node to be its own gateway|
|US6070246 *||Feb 4, 1998||May 30, 2000||3Com Corporation||Method and system for secure cable modem initialization|
|US6185623 *||Nov 7, 1997||Feb 6, 2001||International Business Machines Corporation||Method and system for trivial file transfer protocol (TFTP) subnet broadcast|
|US6691227 *||Sep 8, 2000||Feb 10, 2004||Reefedge, Inc.||Location-independent packet routing and secure access in a short-range wireless networking environment|
|US6717949 *||Aug 31, 1998||Apr 6, 2004||International Business Machines Corporation||System and method for IP network address translation using selective masquerade|
|US7293282 *||Jul 3, 2003||Nov 6, 2007||Time Warner Cable, Inc.||Method to block unauthorized access to TFTP server configuration files|
|US20030187997 *||Mar 27, 2002||Oct 2, 2003||Alan Previn Alexis||Pre-execution environment compliant dynamic host configuration protocol relay agent|
|1||*||Fry et al. A Caching DHCP Relay Agent, Rennsselaer Polytechnic Institute, Oct. 1997, pp. 1-13 .|
|2||*||Fry et al. A Caching DHCP Relay Agent, Rennsselaer Polytechnic Institute, Oct. 1997, pp. 1-13 <http://www.cs.rpi.edu/research/tr/97-10.pdf>.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7984160 *||Mar 5, 2009||Jul 19, 2011||Riverbed Technology, Inc.||Establishing a split-terminated communication connection through a stateful firewall, with network transparency|
|US8180902||Sep 30, 2009||May 15, 2012||Riverbed Technology, Inc.||Establishing network connections between transparent network devices|
|US8181060||Sep 30, 2009||May 15, 2012||Riverbad Technology, Inc.||Preventing data corruption with transparent network connections|
|US8224936 *||May 21, 2008||Jul 17, 2012||Cisco Technology, Inc.||Configuration file override|
|US8255544 *||Jun 2, 2011||Aug 28, 2012||Riverbed Technology, Inc.||Establishing a split-terminated communication connection through a stateful firewall, with network transparency|
|US8335917||Aug 12, 2008||Dec 18, 2012||Cisco Technology, Inc.||System for binding a device to a gateway to regulate service theft through cloning|
|US8473589 *||Jun 7, 2012||Jun 25, 2013||Cisco Technology, Inc.||Configuration file override|
|US20090292795 *||May 21, 2008||Nov 26, 2009||Cisco Technology, Inc||Configuration file override|
|US20100040055 *||Aug 12, 2008||Feb 18, 2010||Cisco Technology, Inc.||System for binding a device to a gateway to regulate service theft through cloning|
|US20100131971 *||Nov 22, 2008||May 27, 2010||Cisco Technology, Inc.||Addressing theft of cable services and breach of cable system and security|
|US20100228867 *||Mar 5, 2009||Sep 9, 2010||Riverbed Technology, Inc.||Establishing a split-terminated communication connection through a stateful firewall, with network transparency|
|US20120246283 *||Jun 7, 2012||Sep 27, 2012||Cisco Technology, Inc||Configuration file override|
|U.S. Classification||370/401, 725/114, 709/203, 709/245, 709/217, 726/2, 725/111|
|International Classification||H04N7/173, G06F15/16, H04L12/28, H04L9/32|
|Cooperative Classification||H04L67/06, H04L41/0866, H04L41/024, H04L61/2015, H04L41/0803|
|European Classification||H04L41/02F, H04L41/08A, H04L61/20A1, H04L29/08N5|
|Feb 28, 2006||AS||Assignment|
Owner name: ARRIS INTERNATIONAL, INC., GEORGIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HOWE, JEFFREY J.;REEL/FRAME:017639/0989
Effective date: 20060228
Owner name: ARRIS INTERNATIONAL, INC.,GEORGIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HOWE, JEFFREY J.;REEL/FRAME:017639/0989
Effective date: 20060228
|Feb 13, 2013||AS||Assignment|
Owner name: ARRIS GROUP, INC., GEORGIA
Free format text: MERGER;ASSIGNOR:ARRIS INTERNATIONAL, INC.;REEL/FRAME:029803/0037
Effective date: 20061101
|Apr 16, 2013||AS||Assignment|
Owner name: ARRIS ENTERPRISES, INC., GEORGIA
Free format text: MERGER;ASSIGNOR:ARRIS GROUP, INC.;REEL/FRAME:030223/0244
Effective date: 20130416
|May 28, 2013||AS||Assignment|
Owner name: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT, IL
Free format text: SECURITY AGREEMENT;ASSIGNORS:ARRIS GROUP, INC.;ARRIS ENTERPRISES, INC.;ARRIS SOLUTIONS, INC.;AND OTHERS;REEL/FRAME:030498/0023
Effective date: 20130417
|Oct 1, 2013||FPAY||Fee payment|
Year of fee payment: 4
|Mar 14, 2017||AS||Assignment|
Owner name: ARRIS ENTERPRISES LLC, PENNSYLVANIA
Free format text: CHANGE OF NAME;ASSIGNOR:ARRIS ENTERPRISES INC;REEL/FRAME:041995/0031
Effective date: 20151231
|Oct 20, 2017||MAFP|
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552)
Year of fee payment: 8