CVE-2012-3749: Infoleak

Published Nov 3, 2012
·
Updated

The extensions APIs in the kernel in Apple iOS before 6.0.1 provide kernel addresses in responses that contain an OSBundleMachOHeaders key, which makes it easier for remote attackers to bypass the ASLR protection mechanism via a crafted app.

Affected Software

41 affected components
apple iPhone OS<=6.0
apple iPhone OS=1.0.0
apple iPhone OS=1.0.1
apple iPhone OS=1.0.2
apple iPhone OS=1.1.0
apple iPhone OS=1.1.1
apple iPhone OS=1.1.2
apple iPhone OS=1.1.3
apple iPhone OS=1.1.4
apple iPhone OS=1.1.5
apple iPhone OS=2.0
apple iPhone OS=2.0.0
apple iPhone OS=2.0.1
apple iPhone OS=2.0.2
apple iPhone OS=2.1
apple iPhone OS=2.1.1
apple iPhone OS=2.2
apple iPhone OS=2.2.1
apple iPhone OS=3.0
apple iPhone OS=3.0.1
apple iPhone OS=3.1
apple iPhone OS=3.1.2
apple iPhone OS=3.1.3
apple iPhone OS=3.2
apple iPhone OS=3.2.1
apple iPhone OS=3.2.2
apple iPhone OS=4.0
apple iPhone OS=4.0.1
apple iPhone OS=4.0.2
apple iPhone OS=4.1
apple iPhone OS=4.2.1
apple iPhone OS=4.2.5
apple iPhone OS=4.2.8
apple iPhone OS=4.3.0
apple iPhone OS=4.3.1
apple iPhone OS=4.3.2
apple iPhone OS=4.3.3
apple iPhone OS=4.3.5
apple iPhone OS=5.0
apple iPhone OS=5.0.1
apple iPhone OS=5.1.1

Event History

Nov 3, 2012
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2012-3749?

CVE-2012-3749 has a medium severity rating as it can allow remote attackers to bypass the ASLR protection mechanism.

2

How do I fix CVE-2012-3749?

To fix CVE-2012-3749, update to iOS version 6.0.1 or later as it contains the necessary security patches.

3

What is the impact of exploiting CVE-2012-3749?

Exploitation of CVE-2012-3749 can potentially allow attackers to gain access to memory addresses, facilitating further attacks on the iOS device.

4

Which devices are affected by CVE-2012-3749?

CVE-2012-3749 affects all iOS versions before 6.0.1, impacting a wide range of Apple devices including iPhones and iPads.

5

Is there any workaround for CVE-2012-3749?

There are no effective workarounds for CVE-2012-3749; the recommended action is to update the operating system.

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