CVE-2008-0085: Infoleak

Published Jul 8, 2008
·
Updated

SQL Server 7.0 SP4, 2000 SP4, 2005 SP1 and SP2, 2000 Desktop Engine (MSDE 2000) SP4, 2005 Express Edition SP1 and SP2, and 2000 Desktop Engine (WMSDE); Microsoft Data Engine (MSDE) 1.0 SP4; and Internal Database (WYukon) SP2 does not initialize memory pages when reallocating memory, which allows database operators to obtain sensitive information (database contents) via unknown vectors related to memory page reuse.

Affected Software

20 affected components
Microsoft SQL Server=2005-sp1
Microsoft Sql Server Desktop Engine=2000-sp4
Microsoft SQL Server=2005-sp1
Microsoft SQL Server=7.0-sp4
Microsoft SQL Server=2005-sp2
Microsoft Data Engine=1.0-sp4
Microsoft SQL Server=2000-sp4
Microsoft SQL Server=2005-sp2
Microsoft SQL Server=2000-sp4
Microsoft SQL Server=2005-sp1
Microsoft SQL Server=2005-sp1
Microsoft SQL Server=2005-sp2
Microsoft SQL Server=2005-sp2
Microsoft WMSDE=2000
Microsoft WYukon=sp2
Microsoft Windows 2003 Server=sp1
Microsoft Windows 2003 Server=sp2
Microsoft WYukon=sp2
Microsoft Windows Server 2003
Microsoft Windows Server 2003=sp2

Event History

Jul 8, 2008
CVE Published
via MITRE·11:00 PM
Data Sourced
via MITRE·11:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2008-0085?

The severity of CVE-2008-0085 is rated as medium due to potential data corruption vulnerabilities.

2

How do I fix CVE-2008-0085?

To fix CVE-2008-0085, apply the latest service packs and updates provided by Microsoft for the affected versions of SQL Server.

3

What software versions are affected by CVE-2008-0085?

CVE-2008-0085 affects Microsoft SQL Server versions 7.0, 2000, 2005, and their respective service packs.

4

What impact does CVE-2008-0085 have?

The impact of CVE-2008-0085 may lead to data corruption and potential unauthorized access through memory exploitation.

5

Is there a workaround for CVE-2008-0085 if I can't apply the update immediately?

If immediate patching is not possible for CVE-2008-0085, it is advised to limit access to the database and closely monitor for any suspicious activity.

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