CVE-2012-3357: Infoleak
Published Jul 22, 2012
·Updated
The SVN revision view (lib/vclib/svn/svnrepos.py) in ViewVC before 1.1.15 does not properly handle log messages when a readable path is copied from an unreadable path, which allows remote attackers to obtain sensitive information, related to a "log msg leak."
Affected Software
33 affected components
viewvc ViewVC<=1.1.14
viewvc ViewVC=0.8
viewvc ViewVC=0.9
viewvc ViewVC=0.9.1
viewvc ViewVC=0.9.2
viewvc ViewVC=0.9.3
viewvc ViewVC=0.9.4
viewvc ViewVC=1.0.0
viewvc ViewVC=1.0.1
viewvc ViewVC=1.0.2
viewvc ViewVC=1.0.3
viewvc ViewVC=1.0.4
viewvc ViewVC=1.0.5
viewvc ViewVC=1.0.6
viewvc ViewVC=1.0.7
viewvc ViewVC=1.0.8
viewvc ViewVC=1.0.9
viewvc ViewVC=1.0.10
viewvc ViewVC=1.0.11
viewvc ViewVC=1.1.0
viewvc ViewVC=1.1.1
viewvc ViewVC=1.1.2
viewvc ViewVC=1.1.3
viewvc ViewVC=1.1.4
viewvc ViewVC=1.1.5
viewvc ViewVC=1.1.6
viewvc ViewVC=1.1.7
viewvc ViewVC=1.1.8
viewvc ViewVC=1.1.9
viewvc ViewVC=1.1.10
viewvc ViewVC=1.1.11
viewvc ViewVC=1.1.12
viewvc ViewVC=1.1.13
Event History
Jul 22, 2012
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2012-3357?
CVE-2012-3357 is classified as a moderate severity vulnerability.
2
How do I fix CVE-2012-3357?
To fix CVE-2012-3357, you should upgrade to ViewVC version 1.1.15 or later.
3
What type of vulnerability is CVE-2012-3357?
CVE-2012-3357 is a information disclosure vulnerability.
4
Which versions of ViewVC are affected by CVE-2012-3357?
ViewVC versions from 0.8 to 1.1.14 are affected by CVE-2012-3357.
5
What kind of information can be leaked due to CVE-2012-3357?
CVE-2012-3357 can leak sensitive log messages due to improper handling of paths.