CVE-2012-4922: Input Validation

Published Sep 14, 2012
·
Updated

The tortimegm function in common/util.c in Tor before 0.2.2.39, and 0.2.3.x before 0.2.3.22-rc, does not properly validate time values, which allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a malformed directory object, a different vulnerability than CVE-2012-4419.

Affected Software

96 affected components
torproject Tor<=0.2.2.38
torproject Tor=0.0.2
torproject Tor=0.0.2-pre13
torproject Tor=0.0.2-pre14
torproject Tor=0.0.2-pre15
torproject Tor=0.0.2-pre16
torproject Tor=0.0.2-pre17
torproject Tor=0.0.2-pre18
torproject Tor=0.0.2-pre19
torproject Tor=0.0.2-pre20
torproject Tor=0.0.2-pre21
torproject Tor=0.0.2-pre22
torproject Tor=0.0.2-pre23
torproject Tor=0.0.2-pre24
torproject Tor=0.0.2-pre25
torproject Tor=0.0.2-pre26
torproject Tor=0.0.2-pre27
torproject Tor=0.0.3
torproject Tor=0.0.4
torproject Tor=0.0.5
torproject Tor=0.0.6
torproject Tor=0.0.6.1
torproject Tor=0.0.6.2
torproject Tor=0.0.7
torproject Tor=0.0.7.1
torproject Tor=0.0.7.2
torproject Tor=0.0.7.3
torproject Tor=0.0.8.1
torproject Tor=0.0.9.1
torproject Tor=0.0.9.2
torproject Tor=0.0.9.3
torproject Tor=0.0.9.4
torproject Tor=0.0.9.5
torproject Tor=0.0.9.6
torproject Tor=0.0.9.7
torproject Tor=0.0.9.8
torproject Tor=0.0.9.9
torproject Tor=0.0.9.10
torproject Tor=0.1.0.10
torproject Tor=0.1.0.11
torproject Tor=0.1.0.12
torproject Tor=0.1.0.13
torproject Tor=0.1.0.14
torproject Tor=0.1.0.15
torproject Tor=0.1.0.16
torproject Tor=0.1.0.17
torproject Tor=0.1.1.20
torproject Tor=0.1.1.21
torproject Tor=0.1.1.22
torproject Tor=0.1.1.23
torproject Tor=0.1.1.24
torproject Tor=0.1.1.25
torproject Tor=0.1.1.26
torproject Tor=0.1.2.13
torproject Tor=0.1.2.14
torproject Tor=0.1.2.15
torproject Tor=0.1.2.16
torproject Tor=0.1.2.17
torproject Tor=0.1.2.18
torproject Tor=0.1.2.19
torproject Tor=0.2.0.30
torproject Tor=0.2.0.31
torproject Tor=0.2.0.32
torproject Tor=0.2.0.33
torproject Tor=0.2.0.34
torproject Tor=0.2.0.35
torproject Tor=0.2.2.18
torproject Tor=0.2.2.19
torproject Tor=0.2.2.20
torproject Tor=0.2.2.21
torproject Tor=0.2.2.22
torproject Tor=0.2.2.23
torproject Tor=0.2.2.24
torproject Tor=0.2.2.25
torproject Tor=0.2.2.26
torproject Tor=0.2.2.27
torproject Tor=0.2.2.28
torproject Tor=0.2.2.29
torproject Tor=0.2.2.30
torproject Tor=0.2.2.31
torproject Tor=0.2.2.32
torproject Tor=0.2.2.33
torproject Tor=0.2.2.34
torproject Tor=0.2.2.35
torproject Tor=0.2.2.36
torproject Tor=0.2.2.37
torproject Tor=0.2.3
torproject Tor=0.2.3.13-alpha
torproject Tor=0.2.3.14-alpha
torproject Tor=0.2.3.15-alpha
torproject Tor=0.2.3.16-alpha
torproject Tor=0.2.3.17-beta
torproject Tor=0.2.3.18-rc
torproject Tor=0.2.3.19-rc
torproject Tor=0.2.3.20-rc
torproject Tor=0.2.3.21-rc

Event History

Sep 14, 2012
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06: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-2012-4922?

CVE-2012-4922 has been classified as a denial of service vulnerability due to its potential to crash the Tor daemon.

2

How do I fix CVE-2012-4922?

To fix CVE-2012-4922, upgrade to Tor version 0.2.3.22-rc or later, which contains the necessary patch.

3

What versions are affected by CVE-2012-4922?

CVE-2012-4922 affects Tor versions before 0.2.2.39 and all 0.2.3.x versions prior to 0.2.3.22-rc.

4

Can CVE-2012-4922 be exploited remotely?

Yes, CVE-2012-4922 can be exploited remotely through a malformed directory object.

5

Is there a workaround for CVE-2012-4922 if I cannot update?

There is no documented workaround for CVE-2012-4922, so updating is the recommended solution.

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