CVE-2008-3895: Infoleak

Published Sep 3, 2008
·
Updated

LILO 22.6.1 and earlier stores pre-boot authentication passwords in the BIOS Keyboard buffer and does not clear this buffer before and after use, which allows local users to obtain sensitive information by reading the physical memory locations associated with this buffer.

Affected Software

62 affected components
LILO LILO=21.7.1
LILO LILO=22.0
LILO LILO=22.3.3
LILO LILO=11
LILO LILO=22.1
LILO LILO=0
LILO LILO=22.0.1
LILO LILO=13
LILO LILO=22.3
LILO LILO=21.7
LILO LILO=14
LILO LILO=7
LILO LILO=4
LILO LILO=22.0.2
LILO LILO=22.3.1
LILO LILO=21.5
LILO LILO=1
LILO LILO=18
LILO LILO=22.5.4
LILO LILO=21.7.2
LILO LILO=21.7.5
LILO LILO=22.5.3.1
LILO LILO=6
LILO LILO<=22.6.1
LILO LILO=22.5.5
LILO LILO=22.5.7
LILO LILO=22.5.1
LILO LILO=22.5.6
LILO LILO=22.2
LILO LILO=22.5.7.2
LILO LILO=19
LILO LILO=22.5.9
LILO LILO=21.4.4
LILO LILO=21.6
LILO LILO=22.6
LILO LILO=3
LILO LILO=21.4.3
LILO LILO=9
LILO LILO=21.6.1
LILO LILO=22.5
LILO LILO=21-3
LILO LILO=21
LILO LILO=16
LILO LILO=12
LILO LILO=21.7.3
LILO LILO=21.5.1
LILO LILO=15
LILO LILO=8
LILO LILO=22.5.2
LILO LILO=21.7.4
LILO LILO=22.3.4
LILO LILO=22.3.2
LILO LILO=20
LILO LILO=10
LILO LILO=22.5.8
LILO LILO=21.4.2
LILO LILO=5
LILO LILO=22.4
LILO LILO=22.4.1
LILO LILO=22.5.3
LILO LILO=2
LILO LILO=17

Event History

Sep 3, 2008
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2008-3895?

CVE-2008-3895 is considered to be of high severity due to the potential exposure of sensitive authentication information.

2

How do I fix CVE-2008-3895?

To fix CVE-2008-3895, upgrade to a version of LILO that is more recent than 22.6.1, as this vulnerability has been addressed in later releases.

3

What are the impacts of CVE-2008-3895?

The impact of CVE-2008-3895 allows local users to access sensitive information stored in the BIOS keyboard buffer, potentially compromising system security.

4

Who is affected by CVE-2008-3895?

CVE-2008-3895 affects all versions of LILO up to and including 22.6.1.

5

Is there a workaround for CVE-2008-3895?

There are no known workarounds for CVE-2008-3895, and the recommended action is to upgrade to a secure version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203