dbcve.org
Cvs SuiteApplication · March Hare

CVE-2010-1326

HIGH · 9.3 CVSS v2.0 Published 2010-09-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
perms.cpp in March Hare Software CVSNT 2.0.58, 2.5.01, 2.5.02, 2.5.03 before build 3736, 2.5.04 before build 2862; CVS Suite 2.5.03, 2008 before build 3736, and 2009 before 3729 allows remote attackers to bypass the permissions check, modify arbitrary modules and directories within CVSROOT, and execute arbitrary code via a crafted branch name ACL, possibly related to incorrect inheritance.

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

Vulnerability in perms.cpp in CVSNT server allows remote attackers to bypass ACL permission checks via a crafted branch name, enabling modification of arbitrary CVSROOT modules/directories and arbitrary code execution. The issue stems from incorrect inheritance in branch name ACL processing.

MitigationUpgrade to CVSNT 2.5.03 build 3736+, 2.5.04 build 2862+, or CVS Suite 2008/2009 to corresponding fixed builds; if immediate upgrade is not feasible, restrict network access to the CVSNT server to reduce attack surface.

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
Cvs SuiteApplication
Affected:= 2.5.03= 2008= 2009
CvsntApplication
Affected:= 2.0.58= 2.5.01= 2.5.02= 2.5.03= 2.5.04

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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. Determine if CVSNT server is installed
    Check for the presence of CVSNT binaries or service. On Windows, look for 'cvsnt' service in Services console (services.msc) or check for cvs.exe/cvsnt.exe in common installation paths like C:\Program Files\cvsnt or C:\Program Files\March Hare. On Linux/Unix, check for /usr/bin/cvs, /usr/bin/cvsnt, or run 'which cvs'
    Affected if CVSNT server is not installed - not affected
  2. Identify CVSNT version
    Run 'cvsnt --version' or 'cvs --version' from the command line, or check the version through the CVSNT Control Panel if installed on Windows. Compare the version number against the affected ranges: Cvs Suite 2.5.03, 2008, 2009; Cvsnt 2.0.58, 2.5.01, 2.5.02, 2.5.03, 2.5.04
    Affected if Installed version matches one of the affected versions listed (2.0.58, 2.5.01, 2.5.02, 2.5.03, 2.5.04 for Cvsnt; 2.5.03, 2008, 2009 for Cvs Suite)
  3. Verify ACL access control is enabled
    Check CVSNT configuration files (typically perms or acl in the CVSROOT directory) or the CVSNT server settings. On Windows, open CVSNT Control Panel > Advanced tab > verify 'Use ACLs' is checked. On Linux, check for 'SystemAuth=no' in config file and presence of perms file in CVSROOT
    Affected if ACL enforcement is enabled - the vulnerability allows bypassing these ACLs, so this configuration makes the flaw applicable
  4. Check network exposure of CVSNT service
    Review firewall rules and network access controls to determine if the CVSNT server port (default 2401/tcp) is accessible from untrusted networks. Use 'netstat -an | grep 2401' or review firewall configuration to confirm listening status and allowed source IPs
    Affected if CVSNT port is exposed to untrusted networks - remote attackers would need network access to exploit the ACL bypass

You are affected if you are running a vulnerable CVSNT or CVS Suite version (2.0.58, 2.5.01-2.5.04, or Cvs Suite 2.5.03/2008/2009) with ACLs enabled and the server is network-accessible to potential attackers.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to CVSNT 2.5.03 build 3736+, 2.5.04 build 2862+, or CVS Suite 2008/2009 to corresponding fixed builds; if immediate upgrade is not feasible, restrict network access to the CVSNT server to reduce attack surface.

Recommended fix High confidence

CVSNT 2.5.04 build 2862 or later (or latest stable); CVS Suite latest stable release

  1. 1. Identify the currently installed CVSNT or CVS Suite version and build number using 'cvs version' or checking the application properties.
  2. 2. For CVSNT 2.0.58, 2.5.01, 2.5.02, or 2.5.03: upgrade to build 3736 or later.
  3. 3. For CVSNT 2.5.04: upgrade to build 2862 or later.
  4. 4. For CVS Suite 2.5.03 or 2008: upgrade to build 3736 or later.
  5. 5. For CVS Suite 2009: upgrade to build 3729 or later.
  6. 6. Alternatively, upgrade to the latest stable release of CVSNT/CVS Suite which incorporates all security fixes.
  7. 7. After upgrading, verify the new build number matches a fixed version.
  8. 8. Test that the ACL permission bypass vulnerability is mitigated by attempting a operation that should be denied under the old vulnerable behavior.
Caveat Major version upgrades may introduce compatibility changes; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cvs Suite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-1326 — 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-2010-1326 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