CVE-2012-3357
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe SVN revision view (lib/vclib/svn/svn_repos.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."
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceViewVC before 1.1.15 contains an information disclosure vulnerability in the SVN revision view (svn_repos.py). When a readable path is copied from an unreadable path, the application improperly handles log messages, allowing attackers to obtain sensitive revision log information they should not have access to.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.1.14= 0.8= 0.9= 0.9.1= 0.9.2= 0.9.3= 0.9.4= 1.0.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed ViewVC versionLocate the ViewVC installation and check the version file (typically viewvc.py, __init__.py, or a VERSION file in the installation directory). Many installations display the version on the login page or error pages.Affected if The installed version is 1.1.14 or earlier, or matches any of these specific versions: 0.8, 0.9, 0.9.1, 0.9.2, 0.9.3, 0.9.4, 1.0.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4.
-
Confirm SVN repository backend is in useCheck the ViewVC configuration file (viewvc.conf or viewvc.ini) for the 'default_cvsroot' or 'default_svn_root' setting, or inspect the svn_repos.py module presence in the ViewVC installation.Affected if ViewVC is configured to serve SVN repositories using the svn_repos.py module.
-
Review SVN path-based access controlsInspect the SVN repository configuration (svnserve.conf or authz files) for any path-level access restrictions where some paths are readable and others are restricted.Affected if The SVN repository has configured access controls that restrict certain paths to specific users while allowing other paths to be publicly or differently accessible.
-
Inspect revision log visibilityUse ViewVC to view SVN revision logs where a commit modified both a restricted path and an accessible path (for example, copying or moving a file from a private directory to a public one).Affected if Log messages from commits affecting restricted paths are visible in the revision history when viewing the accessible copied path.
The environment is affected if ViewVC version 1.1.14 or earlier is installed and it serves SVN repositories with path-based access controls where users can access some paths but not others.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade ViewVC to version 1.1.15 or later. This is a patch-level update that addresses the improper handling of log messages in the SVN revision view when dealing with paths having different access permissions.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3357 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-3357 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data