CVE-2011-1213: Buffer Overflow

Published May 31, 2011
·
Updated

Integer underflow in lzhsr.dll in Autonomy KeyView, as used in IBM Lotus Notes before 8.5.2 FP3, allows remote attackers to execute arbitrary code via a crafted header in a .lzh attachment that triggers a stack-based buffer overflow, aka SPR PRAD88MJ2W.

Affected Software

106 affected components
IBM Lotus Notes<=8.5.2.2
IBM Lotus Notes=3.0
IBM Lotus Notes=3.0.0.1
IBM Lotus Notes=3.0.0.2
IBM Lotus Notes=4.2
IBM Lotus Notes=4.2.1
IBM Lotus Notes=4.2.2
IBM Lotus Notes=4.5
IBM Lotus Notes=4.6
IBM Lotus Notes=4.6.7a
IBM Lotus Notes=4.6.7h
IBM Lotus Notes=5.0
IBM Lotus Notes=5.0.1
IBM Lotus Notes=5.0.1.02
IBM Lotus Notes=5.0.1a
IBM Lotus Notes=5.0.1b
IBM Lotus Notes=5.0.1c
IBM Lotus Notes=5.0.2
IBM Lotus Notes=5.0.2a
IBM Lotus Notes=5.0.2b
IBM Lotus Notes=5.0.2c
IBM Lotus Notes=5.0.3
IBM Lotus Notes=5.0.4
IBM Lotus Notes=5.0.4a
IBM Lotus Notes=5.0.5
IBM Lotus Notes=5.0.5.01
IBM Lotus Notes=5.0.5.02
IBM Lotus Notes=5.0.6
IBM Lotus Notes=5.0.6a
IBM Lotus Notes=5.0.6a.01
IBM Lotus Notes=5.0.7
IBM Lotus Notes=5.0.7a
IBM Lotus Notes=5.0.8
IBM Lotus Notes=5.0.9
IBM Lotus Notes=5.0.9a
IBM Lotus Notes=5.0.10
IBM Lotus Notes=5.0.11
IBM Lotus Notes=5.0.12
IBM Lotus Notes=5.0a
IBM Lotus Notes=5.02
IBM Lotus Notes=6.0
IBM Lotus Notes=6.0.1
IBM Lotus Notes=6.0.1-cf1
IBM Lotus Notes=6.0.1-cf2
IBM Lotus Notes=6.0.1-cf3
IBM Lotus Notes=6.0.2
IBM Lotus Notes=6.0.2-cf1
IBM Lotus Notes=6.0.2-cf2
IBM Lotus Notes=6.0.2.2
IBM Lotus Notes=6.0.3
IBM Lotus Notes=6.0.4
IBM Lotus Notes=6.0.5
IBM Lotus Notes=6.5
IBM Lotus Notes=6.5.1
IBM Lotus Notes=6.5.2
IBM Lotus Notes=6.5.3
IBM Lotus Notes=6.5.3.1
IBM Lotus Notes=6.5.4
IBM Lotus Notes=6.5.4.1
IBM Lotus Notes=6.5.4.2
IBM Lotus Notes=6.5.4.3
IBM Lotus Notes=6.5.5
IBM Lotus Notes=6.5.5.1
IBM Lotus Notes=6.5.5.2
IBM Lotus Notes=6.5.5.3
IBM Lotus Notes=6.5.6
IBM Lotus Notes=6.5.6.1
IBM Lotus Notes=6.5.6.2
IBM Lotus Notes=6.5.6.3
IBM Lotus Notes=7.0
IBM Lotus Notes=7.0.0
IBM Lotus Notes=7.0.1
IBM Lotus Notes=7.0.1.1
IBM Lotus Notes=7.0.2
IBM Lotus Notes=7.0.2.1
IBM Lotus Notes=7.0.2.2
IBM Lotus Notes=7.0.2.3
IBM Lotus Notes=7.0.3
IBM Lotus Notes=7.0.3.1
IBM Lotus Notes=7.0.4
IBM Lotus Notes=7.0.4.0
IBM Lotus Notes=7.0.4.1
IBM Lotus Notes=7.0.4.2
IBM Lotus Notes=8.0
IBM Lotus Notes=8.0.0
IBM Lotus Notes=8.0.1
IBM Lotus Notes=8.0.2
IBM Lotus Notes=8.0.2.0
IBM Lotus Notes=8.0.2.1
IBM Lotus Notes=8.0.2.2
IBM Lotus Notes=8.0.2.3
IBM Lotus Notes=8.0.2.4
IBM Lotus Notes=8.0.2.5
IBM Lotus Notes=8.0.2.6
IBM Lotus Notes=8.5
IBM Lotus Notes=8.5.0.0
IBM Lotus Notes=8.5.0.1
IBM Lotus Notes=8.5.1
IBM Lotus Notes=8.5.1.0
IBM Lotus Notes=8.5.1.1
IBM Lotus Notes=8.5.1.2
IBM Lotus Notes=8.5.1.3
IBM Lotus Notes=8.5.1.4
IBM Lotus Notes=8.5.1.5
IBM Lotus Notes=8.5.2.0
IBM Lotus Notes=8.5.2.1

Event History

May 31, 2011
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08: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-2011-1213?

CVE-2011-1213 is considered critical as it allows remote attackers to execute arbitrary code.

2

How do I fix CVE-2011-1213?

To fix CVE-2011-1213, upgrade IBM Lotus Notes to version 8.5.2 FP3 or later.

3

What type of vulnerability is CVE-2011-1213?

CVE-2011-1213 is an integer underflow vulnerability that leads to a stack-based buffer overflow.

4

Which IBM Lotus Notes versions are affected by CVE-2011-1213?

CVE-2011-1213 affects multiple versions of IBM Lotus Notes prior to 8.5.2 FP3, including versions 4.2 to 8.5.2.

5

Can CVE-2011-1213 be exploited through a network?

Yes, CVE-2011-1213 can be exploited remotely via crafted .lzh attachments.

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