dbcve.org
Snare AgentApplication · Intersect Alliance

CVE-2010-2594

MEDIUM · 6.8 CVSS v2.0 Published 2010-07-02
Fix available
A fix is available. Upgrade to after 3.2.3 or later.
See remediation →
77/100
Remediation priority · High
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
Multiple cross-site request forgery (CSRF) vulnerabilities in the web management interface in InterSect Alliance Snare Agent 3.2.3 and earlier on Solaris, Snare Agent 3.1.7 and earlier on Windows, Snare Agent 1.5.0 and earlier on Linux and AIX, Snare Agent 1.4 and earlier on IRIX, Snare Epilog 1.5.3 and earlier on Windows, and Snare Epilog 1.2 and earlier on UNIX allow remote attackers to hijack the authentication of administrators for requests that (1) change the password or (2) change the listening port.

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

Multiple CSRF vulnerabilities in the web management interface of InterSect Alliance Snare Agent and Snare Epilog allow remote attackers to silently trigger administrative actions (password changes, port modifications) by tricking authenticated administrators into visiting malicious pages. The affected products lack anti-CSRF tokens or protections in their web forms.

MitigationImplement anti-CSRF tokens for all state-changing operations in the web management interface; apply vendor patches if available; restrict access to the management interface to trusted networks only.

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
Snare AgentApplication
Affected:<= 3.2.3= 2.0= 2.1= 2.3= 2.4= 2.5= 2.5.2= 2.5.3= 2.5.4= 2.5.6= 2.5.7= 3.0.0
Snare EpilogApplication
Affected:<= 1.5.3= 1.1= 1.2= 1.3= 1.3.1= 1.3.3= 1.4.0= 1.5.0= 1.5.1= 1.5.2<= 1.2

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

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

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. Identify installed Snare Agent version
    On Linux: check /opt/snare or /var/opt/snare for version files, or run 'snare --version'. On Windows: check registry key HKLM\Software\IntersectAlliance\Snare or the installation directory for version information.
    Affected if The installed version matches <= 3.2.3; = 2.0; = 2.1; = 2.3; = 2.4; = 2.5; = 2.5.2; = 2.5.3; = 2.5.4; = 2.5.6; = 2.5.7; = 3.0.0 or falls within these ranges.
  2. Identify installed Snare Epilog version
    Check the installation directory for version files, or look for epilog version in configuration files under the Snare Epilog installation path.
    Affected if The installed version matches <= 1.5.3; = 1.1; = 1.2; = 1.3; = 1.3.1; = 1.3.3; = 1.4.0; = 1.5.0; = 1.5.1; = 1.5.2; <= 1.2 or falls within these ranges.
  3. Verify web management interface is accessible
    Check if the Snare web interface port (default 6161 for Agent) is listening and accessible. Run 'netstat -an | grep 6161' or 'ss -tlnp | grep 6161' to confirm the service is bound to an interface.
    Affected if The web management interface is enabled and reachable over the network, exposing the CSRF-vulnerable forms.
  4. Confirm administrative forms lack CSRF protection
    Access the web management interface and inspect HTML forms (login, password change, port configuration) for the presence of anti-CSRF tokens. Look for hidden input fields with random tokens or CSRF-specific headers in form submissions.
    Affected if Forms submit without any CSRF token or referer validation, making the application vulnerable to cross-site request forgery.

You are affected if Snare Agent or Snare Epilog is installed at a version within the affected ranges AND the web management interface is enabled and accessible without CSRF token protection in its forms.

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 3.2.3
Interim mitigation

Implement anti-CSRF tokens for all state-changing operations in the web management interface; apply vendor patches if available; restrict access to the management interface to trusted networks only.

Fix this in Snare Agent Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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