Ubuntu.comUB:CVE-2012-6111CVE-2012-6111
5 Medium
CVSS2
Attack Vector
NETWORK
Attack Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:N/AC:L/Au:N/C:P/I:N/A:N
7.5 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
NONE
Availability Impact
NONE
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
0.013 Low
EPSS
Percentile
85.8%
gnome-keyring does not discard stored secrets when using
gnome_keyring_lock_all_sync function
Bugs
- <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697896>
- <https://bugzilla.gnome.org/show_bug.cgi?id=690466>
Notes
| Author | Note |
|---|---|
| mdeslaur | In hardy, gnome_keyring_lock_all_sync() was in the gnome-keyring package, and works as expected. In 2.30+ in Lucid+, gnome_keyring_lock_all_sync() is in libgnome-keyring and sends a LockService DBus call to gnome-keyring. This call isn’t implemented in lucid+ Nothing in the archive in Oneiric+ actually uses gnome_keyring_lock_all_sync(), so this is low. In Lucid, gnome-power-manager calls this before suspend and hibernation with the intention of locking the keyring. Fixing this in Lucid would result in the user likely having to retype their keyring password when coming out of suspend and hibernation, which is an intrusive change this late in Lucid’s lifecycle. Setting this issue as priority low for the reasons above. |
Related
5 Medium
CVSS2
Attack Vector
NETWORK
Attack Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:N/AC:L/Au:N/C:P/I:N/A:N
7.5 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
NONE
Availability Impact
NONE
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
0.013 Low
EPSS
Percentile
85.8%