Asterisk vulnerabilities in chan_skinny.c and chan_sip.c

Bug #66912 reported by magilus
256
Affects Status Importance Assigned to Milestone
asterisk (Ubuntu)
Fix Released
Undecided
Unassigned
Breezy
Invalid
Undecided
Unassigned
Dapper
Fix Released
Undecided
Unassigned
Edgy
Fix Released
Undecided
Unassigned

CVE References

Revision history for this message
magilus (magilus) wrote :

In Feisty, there is 1:1.2.13~dfsg-2ubuntu1, which fixes the issue ( it is a security only release ). This should probably be backported.

Changed in asterisk:
status: Unconfirmed → Fix Released
Revision history for this message
magilus (magilus) wrote :

It seems to successfully build in an Edgy chroot. Sadly, I do not have enough disk space so that I can test the full build procedure. Could anyone try and publish it to Edgy please?

Revision history for this message
Kees Cook (kees) wrote :

Hi! If you can provide the security patch debdiff for the edgy package, I'd be happy to get it published for edgy. It can't be a version update, though; only a security path. For a full version backport, you'll need to go through the MOTU SRU procedures.

Revision history for this message
magilus (magilus) wrote :

I'll try to find one.

In Asterisk 1.2.13, an other issue has been fixed: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-5445

This should be probably fixed, too.

magilus (magilus)
description: updated
Revision history for this message
magilus (magilus) wrote :

CVE 2006-5444 is fixed there:

http://lists.digium.com/pipermail/svn-commits/2006-October/017805.html
http://svn.digium.com/view/asterisk?rev=45332&view=rev

Please recheck if the patch is the correct one. It applies fine to the asterisk_1.2.12.1.dfsg.orig.tar.gz, I didn't make any further investigations.

Revision history for this message
magilus (magilus) wrote :

CVE-2006-5445 is harder to fix, because they applied other patches before which do not have any connection to the security hole. But it also seems that this is not critical, in svn commit #45306 they write

"After some research, we realized that the default behaviour since a long
time was doing the right thing, even though the change optimized a bit
and removed a lot of potential risks.

Conclusion: No need for a configuration option at all."
--> http://svn.digium.com/view/asterisk?rev=45306&view=rev

So I would suggest to only fix CVE-2006-5444.

magilus (magilus)
Changed in asterisk:
status: Unconfirmed → Fix Committed
magilus (magilus)
Changed in asterisk:
status: Fix Committed → Fix Released
magilus (magilus)
Changed in asterisk:
status: Unconfirmed → Fix Committed
Revision history for this message
magilus (magilus) wrote :

I personally do not want to fix this issue for Breezy. If anybody does, feel free to do.

Changed in asterisk:
status: Fix Committed → Fix Released
Revision history for this message
Marco Rodrigues (gothicx) wrote :

Breezy support is over.. Today it's Breezy End Of Life!

Changed in asterisk:
status: Unconfirmed → Rejected
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.