-----BEGIN PGP SIGNED MESSAGE-----
AUSCERT External Security Bulletin Redistribution
ESB-2008.0831 -- [NetBSD]
Malicious PPPoE discovery packet can overrun a kernel buffer
17 September 2008
AusCERT Security Bulletin Summary
Operating System: NetBSD
Impact: Denial of Service
CVE Names: CVE-2008-3584
Revision History: September 17 2008: Added CVE Reference
August 27 2008: Initial Release
- --------------------------BEGIN INCLUDED TEXT--------------------
- -----BEGIN PGP SIGNED MESSAGE-----
NetBSD Security Advisory 2008-010
Topic: Malicious PPPoE discovery packet can overrun a kernel buffer
Version: NetBSD-current: affected
NetBSD 4.0: affected
NetBSD 3.1.*: affected
NetBSD 3.1 affected
NetBSD 3.0.*: affected
NetBSD 3.0: affected
Severity: Remote denial-of-service
Fixed: NetBSD-current: August 08, 2008
NetBSD-4-0 branch: August 08, 2008
(4.0.1 will include the fix)
NetBSD-4 branch: August 08, 2008
(4.1 will include the fix)
NetBSD-3-1 branch: August 08, 2008
(3.1.2 will include the fix)
NetBSD-3-0 branch: August 08, 2008
(3.0.4 will include the fix)
NetBSD-3 branch: August 08, 2008
(3.2 will include the fix)
A problem has been identified in the pppoe(4) code. A bug in range checking
allows a malicious packet to make the kernel access memory outside of the
allocated buffer and cause a kernel crash. It is currently unclear if this
issue could be exploited any further than denial of service.
The critical code deals with early states of a PPPoE connection, before
a session between client and access concentrator has been established.
Packets in this "discovery" phase may consist of multiple variable length
"tags" packed together in a pppoe packet. Each tag is checked and the length
validated against to total packet size. A bug in this length check allowed
packets to advance the next tag pointer to up to 4 bytes beyond the end
of the packet. This can cause a kernel crash.
The problematic code path is executed even without active pppoe(4) interfaces,
as long as at least one has been created with "ifconfig pppoe0 create". No
further configuration of the pppoe(4) interface is needed.
The attack is not routable, so attackers would have to have access to the
LAN of an affected machine - or the DSL side would need to be configured
like a shared ethernet segment. This is uncommon, but done by some providers.
Solutions and Workarounds
The pseudo-device pppoe is present in GENERIC kernels. The system must
be configured with a pppoe(4) instance.
For all NetBSD versions, you need to obtain fixed kernel sources,
rebuild and install the new kernel, and reboot the system.
The fixed source may be obtained from the NetBSD CVS repository.
The following instructions briefly summarise how to upgrade your
kernel. In these instructions, replace:
ARCH with your architecture (from uname -m), and
KERNCONF with the name of your kernel configuration file.
To update from CVS, re-build, and re-install the kernel:
# cd src
# cvs update -d -P sys/net/if_spppsubr.c
# ./build.sh kernel=KERNCONF
# mv /netbsd /netbsd.old
# cp sys/arch/ARCH/compile/obj/KERNCONF/netbsd /netbsd
# shutdown -r now
For more information on how to do this, see:
Yasuoka Masahiko from Internet Initiative Japan Inc. for discovering the
problem and providing a fix.
2008-08-26 Initial release
Advisories may be updated as new information becomes available.
The most recent version of this advisory (PGP signed) can be found at
Information about NetBSD and NetBSD security can be found at
http://www.NetBSD.org/ and http://www.NetBSD.org/Security/.
Copyright 2008, The NetBSD Foundation, Inc. All Rights Reserved.
Redistribution permitted only in full, unmodified form.
$NetBSD: NetBSD-SA2008-010.txt,v 1.1 2008/08/25 22:51:57 adrianp Exp $
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (NetBSD)
- -----END PGP SIGNATURE-----
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to firstname.lastname@example.org
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
If you believe that your computer system has been compromised or attacked in
any way, we encourage you to let us know by completing the secure National IT
Incident Reporting Form at:
Australian Computer Emergency Response Team
The University of Queensland
Internet Email: email@example.com
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----