dbcve.org
ViewvcApplication

CVE-2012-3356

MEDIUM · 5.0 CVSS v2.0 Published 2012-07-22
Fix available
A fix is available. Upgrade to after 1.1.14 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The remote SVN views functionality (lib/vclib/svn/svn_ra.py) in ViewVC before 1.1.15 does not properly perform authorization, which allows remote attackers to bypass intended access restrictions via unspecified vectors.

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 confidence

ViewVC before 1.1.15 contains an authorization bypass vulnerability in the SVN remote access (svn_ra.py) module. The remote SVN views functionality fails to properly enforce authorization checks, allowing remote attackers to bypass intended access restrictions and potentially view unauthorized repository content.

MitigationUpgrade ViewVC to version 1.1.15 or later. After upgrading, review and verify that the SVN repository authorization settings in the configuration are properly enforced.

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
ViewvcApplication
Affected:<= 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.4

CVSS 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
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/I:P/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate ViewVC installation and version file
    Search for ViewVC in common locations such as /usr/local/viewvc, /var/www/viewvc, or within the web server's document root. Look for a file named 'viewvc.py' or 'lib/viewvc.py' and check the version information typically found in a 'VERSION' file or within the main module header.
    Affected if ViewVC is installed and the version is 1.1.14 or earlier, or matches any of these: 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.4.
  2. Identify the ViewVC configuration file
    Find the viewvc.conf or viewvc.conf.in file in the ViewVC installation directory, commonly located in a 'conf' subdirectory alongside the main installation.
    Affected if The configuration file exists and the SVN remote access module is enabled.
  3. Verify if SVN remote access (svn_ra) is enabled
    Open the ViewVC configuration file and search for the 'svn_ra' section or 'enable_svn_remote_access' setting. Check for 'svn_repos' or 'root_orphan' parameters that enable remote SVN repository access.
    Affected if The svn_ra module or remote SVN access is explicitly enabled in the configuration.
  4. Inspect SVN repository path configuration
    In the configuration file, locate the 'svn_repos' parameter or 'root_orphan' setting which defines the SVN repository path(s) accessible through ViewVC's remote access feature.
    Affected if One or more SVN repository paths are configured for remote access through ViewVC.
  5. Confirm authorization configuration for remote access
    Review the ViewVC configuration for any authorization-related settings such as 'authz' or 'authorizer' configuration sections that apply to the SVN remote access paths. Note whether these are properly configured or missing.
    Affected if Authorization settings for svn_ra are absent, misconfigured, or not applied to the configured remote access paths.

A user is affected if ViewVC version 1.1.14 or earlier (or any version 0.8 through 1.0.4) is installed with the SVN remote access (svn_ra) module enabled and configured, and the authorization checks for remote repository access are not properly enforced.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.1.14
Interim mitigation

Upgrade ViewVC to version 1.1.15 or later. After upgrading, review and verify that the SVN repository authorization settings in the configuration are properly enforced.

Fix this in Viewvc Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-3356 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-3356 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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