Anyone seen this before on an SBC firmware model?

Started by Rik, Apr 14, 2008, 17:54:25

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Rik

From the detailed log:

INF       2008-04-08T04:21:39+01:00      pkg:  scheduled 1 updates and 0 removes
INF    2008-04-08T04:21:40+01:00    pkg:  starting schedule
INF    2008-04-08T04:21:40+01:00    pkg:  starting update uiupdate/generic.hotfix
INF    2008-04-08T04:21:45+01:00    cwmd:  pkg 12 operation recorded
INF    2008-04-08T04:21:45+01:00    pkg:  extracted uiupdate/generic.hotfix
INF    2008-04-08T04:21:52+01:00    pkg:  state set to done, operation finished
INF    2008-04-08T04:21:52+01:00    cwmd:  pkgset operation recorded
INF    2008-04-09T04:21:40+01:00    initd:  stopping runlevel: 9 => 0
INF    2008-04-09T04:21:40+01:00    initd:  cwmd stop pid:38
WRN    2008-04-09T04:21:40+01:00    lmd:  cms0: cwmd pipe closed
WRN    2008-04-09T04:21:40+01:00    cwmd:  exit pid: 38
WRN    2008-04-09T04:21:40+01:00    lmd:  cms0: cwmd pipe closed
INF    2008-04-09T04:21:40+01:00    initd:  stopping runlevel: 8 => 0
INF    2008-04-09T04:21:40+01:00    initd:  sntpcd stop pid:37
INF    2008-04-09T04:21:40+01:00    initd:  stopping runlevel: 7 => 0
INF    2008-04-09T04:21:40+01:00    initd:  pkgc stop
INF    2008-04-09T04:21:40+01:00    initd:  rfsd stop pid:25
INF    2008-04-09T04:21:40+01:00    initd:  httpd stop pid:26
WRN    2008-04-09T04:21:40+01:00    httpd:  poll error - Interrupted system call
INF    2008-04-09T04:21:40+01:00    initd:  hostapd stop pid:36
INF    2008-04-09T04:21:40+01:00    hostapd:  Signal 15 received - terminating
INF    2008-04-09T04:21:40+01:00    httpd:  vhost down on 127.0.0.1 port: 80
INF    2008-04-09T04:21:40+01:00    httpd:  vhost down on 0.0.0.0 port: 25
INF    2008-04-09T04:21:40+01:00    httpd:  vhost down on 192.168.1.254 port: 80
INF    2008-04-09T04:21:40+01:00    initd:  ssdpd stop pid:28
INF    2008-04-09T04:21:40+01:00    httpd:  vhost down on 192.168.1.254 port: 443
INF    2008-04-09T04:21:40+01:00    httpd:  vhost down on 212.xx.xx.xx port: 50001
WRN    2008-04-09T04:21:40+01:00    httpd:  process[26] stopped
INF    2008-04-09T04:21:40+01:00    initd:  stopping runlevel: 6 => 0
INF    2008-04-09T04:21:40+01:00    nodesd:  process[21] stopped
INF    2008-04-09T04:21:40+01:00    initd:  nodesd stop pid:21
INF    2008-04-09T04:21:40+01:00    initd:  dhcpd stop pid:22
INF    2008-04-09T04:21:40+01:00    initd:  named stop pid:23
INF    2008-04-09T04:21:40+01:00    initd:  stopping runlevel: 5 => 0
INF    2008-04-09T04:21:40+01:00    initd:  lmd stop pid:20
INF    2008-04-09T04:21:40+01:00    lmd:  ipnet1: DOWN on bridge0 with 192.168.1.254
INF    2008-04-09T04:21:40+01:00    lmd:  ipnet0: DOWN on ppp0 with 212.xx.xx.xx
INF    2008-04-09T04:21:40+01:00    lmd:  exiting status: 0
INF    2008-04-09T04:21:40+01:00    initd:  stopping runlevel: 4 => 0
INF    2008-04-09T04:21:40+01:00    initd:  pkg stop pid:14
INF    2008-04-09T04:21:40+01:00    initd:  pkgc stop
INF    2008-04-09T04:21:40+01:00    initd:  login stop pid:17
INF    2008-04-09T04:21:40+01:00    initd:  pki stop
INF    2008-04-09T04:21:40+01:00    initd:  syslogd stop pid:19
INF    2008-04-09T04:21:40+01:00    syslog:  syslogd exiting...
INF    2008-04-09T04:21:40+01:00    initd:  stopping runlevel: 3 => 0
INF    2008-04-09T04:21:40+01:00    initd:  libulib stop
INF    2008-04-09T04:21:40+01:00    initd:  libmif stop
INF    2008-04-09T04:21:40+01:00    initd:  stopping runlevel: 2 => 0
INF    2008-04-09T04:21:40+01:00    initd:  stopping runlevel: 1 => 0
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

Sorry Rik, I have not noticed anything like that
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

I'm just wondering what update it was making - I'm not keen on things updating themselves without me agreeing.  :o
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Lance

Maybe its a fix for the security loophole... who knows!!!
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Indeed - it would be nice if they put a narrative in explaining the upgrade, wouldn't it...
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Lance

Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

I'll check mine when I get home, Rik. I take it the firmware version hasn't changed?

Rik

No, that's the first thing I checked. I tried Googling, too, but only found references to Windows, not the router, when it came to hotfixes. :(
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

I've checked the log and I've got nothing like that in mine, Rik. ???

Rik

Odd, isn't it. I've never seen anything like it before, and just happened to look today...
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

It is. If you click the upgrade link on the router home page, does it says there's no update available?

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby


Rik

Odd, isn't it. Maybe, as Lance says, it's a fix for the password problem.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

That would certainly be nice, but you'd think the firmware version would change (or that would certainly be logical). Hmm...

Rik

Perhaps they regard it like Windows, a security patch doesn't change the version?  :stars:
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

Right, I've had a read of this page, which seems to suggest there is a hotfix floating about (and that the firmware version doesn't change).

Going by what they say, I think I have it, but it's difficult to say. I guess the best way would be for me to test the vulnerability, which I'll do shortly. ;)

[attachment deleted by admin]

Rik

Nice find, Sebby, and mine looks just like yours.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Simon

My detailed log is still full of these, and nothing much else:

WRN       2008-04-14T14:44:07+01:00      cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T14:44:07+01:00    cwmd:  session failed...
INF    2008-04-14T14:44:07+01:00    cwmd:  session will be retried in 299186(ms)
INF    2008-04-14T14:49:07+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T14:50:07+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T14:50:07+01:00    cwmd:  session failed...
INF    2008-04-14T14:50:07+01:00    cwmd:  session will be retried in 253594(ms)
INF    2008-04-14T14:54:37+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T14:55:37+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T14:55:37+01:00    cwmd:  session failed...
INF    2008-04-14T14:55:37+01:00    cwmd:  session will be retried in 338388(ms)
INF    2008-04-14T15:01:20+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T15:02:20+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T15:02:20+01:00    cwmd:  session failed...
INF    2008-04-14T15:02:20+01:00    cwmd:  session will be retried in 349159(ms)
INF    2008-04-14T15:08:20+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T15:09:20+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T15:09:20+01:00    cwmd:  session failed...
INF    2008-04-14T15:09:20+01:00    cwmd:  session will be retried in 269523(ms)
INF    2008-04-14T15:13:50+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T15:14:50+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T15:14:50+01:00    cwmd:  session failed...
INF    2008-04-14T15:14:50+01:00    cwmd:  session will be retried in 282987(ms)
INF    2008-04-14T15:19:37+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T15:20:37+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T15:20:37+01:00    cwmd:  session failed...
INF    2008-04-14T15:20:37+01:00    cwmd:  session will be retried in 260548(ms)
INF    2008-04-14T15:25:07+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T15:26:07+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T15:26:07+01:00    cwmd:  session failed...
INF    2008-04-14T15:26:07+01:00    cwmd:  session will be retried in 278332(ms)
INF    2008-04-14T15:30:50+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T15:31:50+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T15:31:50+01:00    cwmd:  session failed...
INF    2008-04-14T15:31:50+01:00    cwmd:  session will be retried in 281632(ms)
INF    2008-04-14T15:36:37+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T15:37:37+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T15:37:37+01:00    cwmd:  session failed...
INF    2008-04-14T15:37:37+01:00    cwmd:  session will be retried in 220633(ms)
INF    2008-04-14T15:41:20+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T15:42:20+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T15:42:20+01:00    cwmd:  session failed...
INF    2008-04-14T15:42:20+01:00    cwmd:  session will be retried in 268497(ms)
INF    2008-04-14T15:46:50+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T15:47:50+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T15:47:50+01:00    cwmd:  session failed...
INF    2008-04-14T15:47:50+01:00    cwmd:  session will be retried in 260272(ms)
INF    2008-04-14T15:52:20+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T15:53:20+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T15:53:20+01:00    cwmd:  session failed...
INF    2008-04-14T15:53:20+01:00    cwmd:  session will be retried in 264538(ms)
INF    2008-04-14T15:57:50+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T15:58:50+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T15:58:50+01:00    cwmd:  session failed...
INF    2008-04-14T15:58:50+01:00    cwmd:  session will be retried in 326829(ms)
INF    2008-04-14T16:04:20+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T16:05:20+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T16:05:20+01:00    cwmd:  session failed...
INF    2008-04-14T16:05:20+01:00    cwmd:  session will be retried in 204669(ms)
INF    2008-04-14T16:08:50+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T16:09:50+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T16:09:50+01:00    cwmd:  session failed...
INF    2008-04-14T16:09:50+01:00    cwmd:  session will be retried in 265018(ms)
INF    2008-04-14T16:14:20+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T16:15:20+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T16:15:20+01:00    cwmd:  session failed...
INF    2008-04-14T16:15:20+01:00    cwmd:  session will be retried in 288361(ms)
INF    2008-04-14T16:20:20+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T16:21:20+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T16:21:20+01:00    cwmd:  session failed...
INF    2008-04-14T16:21:20+01:00    cwmd:  session will be retried in 342020(ms)
INF    2008-04-14T16:27:07+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T16:28:07+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T16:28:07+01:00    cwmd:  session failed...
INF    2008-04-14T16:28:07+01:00    cwmd:  dns query 220711008831.bootstrap.cms.2wire.com on retry 191
INF    2008-04-14T16:28:07+01:00    cwmd:  session will be retried in 305827(ms)
INF    2008-04-14T16:33:20+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T16:34:20+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T16:34:20+01:00    cwmd:  session failed...
INF    2008-04-14T16:34:20+01:00    cwmd:  session will be retried in 346733(ms)
INF    2008-04-14T16:40:07+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T16:41:07+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T16:41:07+01:00    cwmd:  session failed...
INF    2008-04-14T16:41:07+01:00    cwmd:  session will be retried in 185551(ms)
INF    2008-04-14T16:44:20+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T16:45:20+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T16:45:20+01:00    cwmd:  session failed...
INF    2008-04-14T16:45:20+01:00    cwmd:  session will be retried in 262832(ms)
INF    2008-04-14T16:49:50+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T16:50:50+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T16:50:50+01:00    cwmd:  session failed...
INF    2008-04-14T16:50:50+01:00    cwmd:  session will be retried in 356761(ms)
INF    2008-04-14T16:56:50+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T16:57:50+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T16:57:50+01:00    cwmd:  session failed...
INF    2008-04-14T16:57:50+01:00    cwmd:  session will be retried in 318634(ms)
INF    2008-04-14T17:03:20+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T17:04:20+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T17:04:20+01:00    cwmd:  session failed...
INF    2008-04-14T17:04:20+01:00    cwmd:  session will be retried in 320628(ms)
INF    2008-04-14T17:09:50+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T17:10:50+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T17:10:50+01:00    cwmd:  session failed...
INF    2008-04-14T17:10:50+01:00    cwmd:  session will be retried in 241456(ms)
INF    2008-04-14T17:15:07+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T17:16:07+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T17:16:07+01:00    cwmd:  session failed...
INF    2008-04-14T17:16:07+01:00    cwmd:  session will be retried in 277055(ms)
INF    2008-04-14T17:20:50+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T17:21:50+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T17:21:50+01:00    cwmd:  session failed...
INF    2008-04-14T17:21:50+01:00    cwmd:  session will be retried in 185949(ms)
INF    2008-04-14T17:25:08+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T17:26:08+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T17:26:08+01:00    cwmd:  session failed...
INF    2008-04-14T17:26:08+01:00    cwmd:  session will be retried in 306747(ms)
INF    2008-04-14T17:31:20+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
WRN    2008-04-14T17:32:20+01:00    cwmd:  httpc_poll_dispatch - Connection timed out
WRN    2008-04-14T17:32:20+01:00    cwmd:  session failed...
INF    2008-04-14T17:32:20+01:00    cwmd:  session will be retried in 298953(ms)
INF    2008-04-14T17:37:20+01:00    cwmd:  retried session started, server: 'https://cwmp.cms.smehomehubrms.bt.com', event code(s): '0 BOOTSTRAP'
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Clearly, you need to buy some laces, Simon. ;)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

The second exploit on that page still works on mine, though...

Simon

Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Quote from: Sebby on Apr 14, 2008, 19:29:07
The second exploit on that page still works on mine, though...

So I wonder what it did fix? :(
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

johnny5

Quote from: Rik on Apr 14, 2008, 19:14:52
and mine looks just like yours.



That's worth a sid james!



Nothing like that on my log! ;D

[attachment deleted by admin]

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

Quote from: Rik on Apr 14, 2008, 19:46:08
So I wonder what it did fix? :(

Not sure, but at least we now know how hotfixes work. Perhaps we'll see another listed soon.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.