CVE-2012-5146: Medium severity suse linux vulnerability
Published Jan 15, 2013
·Updated
Google Chrome before 24.0.1312.52 allows remote attackers to bypass the Same Origin Policy via a malformed URL.
Affected Software
114 affected components
openSUSE openSUSE=12.1
openSUSE openSUSE=12.2
Google Chrome<=24.0.1312.51
Google Chrome=24.0.1272.0
Google Chrome=24.0.1272.1
Google Chrome=24.0.1273.0
Google Chrome=24.0.1274.0
Google Chrome=24.0.1275.0
Google Chrome=24.0.1276.0
Google Chrome=24.0.1276.1
Google Chrome=24.0.1277.0
Google Chrome=24.0.1278.0
Google Chrome=24.0.1279.0
Google Chrome=24.0.1280.0
Google Chrome=24.0.1281.0
Google Chrome=24.0.1281.1
Google Chrome=24.0.1281.2
Google Chrome=24.0.1281.3
Google Chrome=24.0.1282.0
Google Chrome=24.0.1283.0
Google Chrome=24.0.1284.0
Google Chrome=24.0.1284.1
Google Chrome=24.0.1284.2
Google Chrome=24.0.1285.0
Google Chrome=24.0.1285.1
Google Chrome=24.0.1285.2
Google Chrome=24.0.1286.0
Google Chrome=24.0.1286.1
Google Chrome=24.0.1287.0
Google Chrome=24.0.1287.1
Google Chrome=24.0.1288.0
Google Chrome=24.0.1288.1
Google Chrome=24.0.1289.0
Google Chrome=24.0.1289.1
Google Chrome=24.0.1290.0
Google Chrome=24.0.1291.0
Google Chrome=24.0.1292.0
Google Chrome=24.0.1293.0
Google Chrome=24.0.1294.0
Google Chrome=24.0.1295.0
Google Chrome=24.0.1296.0
Google Chrome=24.0.1297.0
Google Chrome=24.0.1298.0
Google Chrome=24.0.1299.0
Google Chrome=24.0.1300.0
Google Chrome=24.0.1301.0
Google Chrome=24.0.1301.2
Google Chrome=24.0.1302.0
Google Chrome=24.0.1303.0
Google Chrome=24.0.1304.0
Google Chrome=24.0.1304.1
Google Chrome=24.0.1305.0
Google Chrome=24.0.1305.1
Google Chrome=24.0.1305.2
Google Chrome=24.0.1305.3
Google Chrome=24.0.1305.4
Google Chrome=24.0.1306.0
Google Chrome=24.0.1306.1
Google Chrome=24.0.1307.0
Google Chrome=24.0.1307.1
Google Chrome=24.0.1308.0
Google Chrome=24.0.1309.0
Google Chrome=24.0.1310.0
Google Chrome=24.0.1311.0
Google Chrome=24.0.1311.1
Google Chrome=24.0.1312.0
Google Chrome=24.0.1312.1
Google Chrome=24.0.1312.4
Google Chrome=24.0.1312.5
Google Chrome=24.0.1312.6
Google Chrome=24.0.1312.7
Google Chrome=24.0.1312.8
Google Chrome=24.0.1312.9
Google Chrome=24.0.1312.10
Google Chrome=24.0.1312.11
Google Chrome=24.0.1312.12
Google Chrome=24.0.1312.13
Google Chrome=24.0.1312.14
Google Chrome=24.0.1312.15
Google Chrome=24.0.1312.16
Google Chrome=24.0.1312.17
Google Chrome=24.0.1312.18
Google Chrome=24.0.1312.19
Google Chrome=24.0.1312.20
Google Chrome=24.0.1312.21
Google Chrome=24.0.1312.22
Google Chrome=24.0.1312.23
Google Chrome=24.0.1312.24
Google Chrome=24.0.1312.25
Google Chrome=24.0.1312.26
Google Chrome=24.0.1312.27
Google Chrome=24.0.1312.28
Google Chrome=24.0.1312.29
Google Chrome=24.0.1312.30
Google Chrome=24.0.1312.31
Google Chrome=24.0.1312.32
Google Chrome=24.0.1312.33
Google Chrome=24.0.1312.34
Google Chrome=24.0.1312.35
Google Chrome=24.0.1312.36
Google Chrome=24.0.1312.37
Google Chrome=24.0.1312.38
Google Chrome=24.0.1312.39
Google Chrome=24.0.1312.40
Google Chrome=24.0.1312.41
Google Chrome=24.0.1312.42
Google Chrome=24.0.1312.43
Google Chrome=24.0.1312.44
Google Chrome=24.0.1312.45
Google Chrome=24.0.1312.46
Google Chrome=24.0.1312.47
Google Chrome=24.0.1312.48
Google Chrome=24.0.1312.49
Google Chrome=24.0.1312.50
Event History
Jan 15, 2013
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2012-5146?
CVE-2012-5146 has been classified with high severity due to its ability to allow attackers to bypass the Same Origin Policy.
2
How do I fix CVE-2012-5146?
To fix CVE-2012-5146, users should update Google Chrome to version 24.0.1312.52 or later.
3
What versions of Google Chrome are affected by CVE-2012-5146?
CVE-2012-5146 affects all versions of Google Chrome before 24.0.1312.52.
4
Which operating systems are impacted by CVE-2012-5146?
CVE-2012-5146 impacts users of Google Chrome on various operating systems, including specific versions of openSUSE.
5
Is there a workaround for CVE-2012-5146 if I can't update immediately?
There are no effective workarounds for CVE-2012-5146; updating to the latest version is the best course of action.