dbcve.org
SambaApplication

CVE-2011-2411

HIGH · 9.0 CVSS v2.0 Published 2011-10-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable 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
Unspecified vulnerability on HP NonStop Servers with software H06.x through H06.23.00 and J06.x through J06.12.00, when Samba is used, allows remote authenticated users to execute arbitrary code via unknown 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 · moderate confidence

Remote code execution vulnerability in HP NonStop Servers (H06.x-H06.23.00 and J06.x-J06.12.00) when Samba is enabled, allowing authenticated remote attackers to execute arbitrary code via unspecified vectors.

MitigationUpgrade HP NonStop Server software to patched versions beyond H06.23.00/J06.12.00, or disable Samba if not required; restrict network access to authenticated users 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
SambaApplication
Affected:all versions
Nonstop ServerHardware / appliance
Affected:all versions
Nonstop Server SoftwareApplication
Affected:= h06.15.00= h06.15.01= h06.15.02= h06.16.00= h06.16.01= h06.16.02= h06.17.00= h06.17.01= h06.17.02= h06.17.03= h06.18.00= h06.18.01

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
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/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 Samba is enabled on the HP NonStop Server
    Inspect the system configuration or running services to determine whether the Samba service is active. On HP NonStop Servers, this may involve checking system files, configuration panels, or using system management commands to list active services.
    Affected if Samba is enabled and running on the system (the vulnerability only applies when Samba is active)
  2. Determine the HP NonStop Server software version
    Use system commands or inspect system information files to obtain the installed HP NonStop Server version. On HP NonStop systems, this is typically retrieved via version inquiry commands or system configuration displays.
    Affected if The installed version falls within H06.x through H06.23.00 or J06.x through J06.12.00 (or matches any of the specifically listed versions: H06.15.00 through H06.18.01)
  3. Confirm Samba component version if accessible
    If possible, query the Samba version running on the system. The CVE states all versions of Samba are affected when running on these HP NonStop Server versions.
    Affected if Samba is present and accessible on the system

The system is affected if Samba is enabled AND the HP NonStop Server version is within the vulnerable range (H06.x-H06.23.00 or J06.x-J06.12.00). If Samba is disabled, the vulnerability does not apply regardless of version.

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 HP NonStop Server software to patched versions beyond H06.23.00/J06.12.00, or disable Samba if not required; restrict network access to authenticated users only.

Recommended fix High confidence

HP NonStop Server software H06.23.00 or J06.12.00 (or later)

  1. 1. Identify the current HP NonStop Server software version (H06.x or J06.x)
  2. 2. If running H06.x versions before H06.23.00, upgrade to H06.23.00 or later
  3. 3. If running J06.x versions before J06.12.00, upgrade to J06.12.00 or later
  4. 4. Obtain the patch from HP IT Resource Center (www.itrc.hp.com)
  5. 5. Apply the patch following HP's standard NonStop Server update procedures
  6. 6. After upgrade, verify Samba configuration and test that the service operates normally
Caveat Upgrading NonStop Server software may require system downtime and should be thoroughly tested in a non-production environment first

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

Fix this in Samba Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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