dbcve.org
Digital Security AuditsApplication · Eeye

CVE-2011-3337

MEDIUM · 6.9 CVSS v2.0 Published 2012-01-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
eEye Audit ID 2499 in eEye Digital Security Audits 2406 through 2423 for eEye Retina Network Security Scanner on HP-UX, IRIX, and Solaris allows local users to gain privileges via a Trojan horse gauntlet program in an arbitrary directory under /usr/local/.

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 · moderate confidence

This is a local privilege escalation vulnerability in eEye Retina Network Security Scanner on HP-UX, IRIX, and Solaris. Local users can gain elevated privileges by placing a Trojan horse program (referred to as 'gauntlet') in any directory under /usr/local/. The scanner appears to execute programs from this directory with elevated privileges.

MitigationAudit and remove any unauthorized or suspicious executables under /usr/local/ directories, verify integrity of the Retina Network Security Scanner installation files, and restrict write access to /usr/local/ to prevent unauthorized program placement.

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
Digital Security AuditsApplication
Affected:= 2406= 2423
Retina Network Security ScannerApplication
Affected:all versions

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

AV:L/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. Verify if Retina Network Security Scanner is installed
    Look for the presence of eEye Retina Network Security Scanner on the system. Check common installation directories or use system package management tools to list installed software. On HP-UX, IRIX, and Solaris, examine standard installation paths for the Retina scanner.
    Affected if The product eEye Retina Network Security Scanner is found installed on the system
  2. Determine the installed version of Retina
    Locate the version information for the installed Retina scanner. This may be in a version file, binary metadata, or obtainable via a version flag if the tool has one. Compare your version against 2406 and 2423.
    Affected if The installed version is 2406 or 2423, or if the version cannot be determined but the scanner is present (since all versions are affected)
  3. Inspect /usr/local/ for suspicious executables
    Search /usr/local/ and all subdirectories for unknown or recently added executable files, particularly any file named 'gauntlet' or other unexpected binaries. Use commands like 'find /usr/local/ -type f -executable' to list all executables.
    Affected if Unexpected or unauthorized executables are found in any directory under /usr/local/
  4. Check write permissions on /usr/local/ directories
    Review the permissions on /usr/local/ and its subdirectories to determine if unprivileged users can write to these locations. Use 'ls -la /usr/local/' and check for world-writable or group-writable permissions.
    Affected if Unprivileged users have write access to directories under /usr/local/ where the scanner executes programs

A user is affected if eEye Retina Network Security Scanner is installed on HP-UX, IRIX, or Solaris, regardless of version, and untrusted users have write access to /usr/local/ directories where suspicious executables could be placed.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Audit and remove any unauthorized or suspicious executables under /usr/local/ directories, verify integrity of the Retina Network Security Scanner installation files, and restrict write access to /usr/local/ to prevent unauthorized program placement.

Fix this in Digital Security Audits Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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