Bug 3630 – Bad UPnP packets crash slimserver

Bug 3630 - Bad UPnP packets crash slimserver

Summary:

Bad UPnP packets crash slimserver

Status:	CLOSED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Misc
Version:	6.3.0
Platform:	PC Linux (other)

Importance:	P1 normal (vote)
Target Milestone:	---
Assigned To:	Andy Grundman

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2006-06-24 09:46 UTC by Tim Hunt
Modified:	2008-09-15 14:38 UTC (History)
CC List:	2 users (show)

See Also:
Category:	---

Attachments
Tcpdump of traffic (8.13 KB, text/plain) 2006-06-24 09:47 UTC, Tim Hunt	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Tim Hunt 2006-06-24 09:46:34 UTC

To be fair, the DVD player is a Momitsu V880n network connected player.

The only message in /tmp/slimserver.log is 'no element found'

It looks like the DVD player is broadcasting multicast packets during the power-on sequence - I assume the DVD player is  looking for its server.

I've attached a tcpdump of traffic to/from this device during the power-on sequence.

I initially noticed the problem in the 6.3 2006-06-21 nightly, an upgrade to 6.3 2006-06-24 didn't fix the problem.

Previous version that I know did not have a problem was 6.1.2

Comment 1 Tim Hunt 2006-06-24 09:47:29 UTC

Created attachment 1282 [details]
Tcpdump of traffic

Comment 2 Tim Hunt 2006-06-24 12:19:08 UTC

I did a little more research on this - UDP port 1900 is used by UPnP and it looks like the error message comes from the XML parser dying because of badly formed XML. SO I'm guessing the real problem is that malformed UPnP packets can crash slimserver.

Comment 3 Andy Grundman 2006-06-24 15:28:11 UTC

I'll take this one.

Comment 4 Andy Grundman 2006-06-26 10:33:01 UTC

Fixed.  Please test tonight's build with your DVD player on the network.

Comment 5 Tim Hunt 2006-06-27 05:07:16 UTC

That seems to have fixed it - Thanks

Comment 6 Chris Owens 2006-06-27 14:21:39 UTC

This bug fix is now part of a released version, and so has been marked closed. If you are still experiencing this problem, please reopen the bug.