dbcve.org
SolarisOperating system · Oracle

CVE-2011-3534

MEDIUM · 5.0 CVSS v2.0 Published 2011-10-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Unspecified vulnerability in Oracle Solaris 8, 9, 10, and 11 Express allows remote attackers to affect availability via unknown vectors related to Network Status Monitor (statd).

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

Vulnerability in Oracle Solaris Network Status Monitor (statd) allows remote attackers to impact availability. The statd daemon is part of NFS locking services and this unspecified vulnerability affects Solaris versions 8 through 11 Express. CVSS 5 indicates network-exploitable with low complexity and no authentication required for availability impact.

MitigationApply Oracle critical patch updates for the affected Solaris versions. If patches are unavailable for end-of-life versions, consider upgrading to a supported Solaris release or disabling statd if not required for NFS operations.

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
SolarisOperating system
Affected:= 8= 9= 10= 11_express

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

AV:N/AC:L/Au:N/C:N/I:N/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 Solaris version
    Run `uname -a` or `cat /etc/release` to display the installed Oracle Solaris version
    Affected if The version shown is 8, 9, 10, or 11 Express (any build)
  2. Determine if statd is running
    Run `svcs -a | grep statd` (for Solaris 10/11) or check the process with `ps -ef | grep statd`
    Affected if The statd daemon process is listed as running or online
  3. Check if statd is enabled via inetd
    Run `grep -i statd /etc/inetd.conf` to see if statd is configured in inetd
    Affected if A line containing 'statd' is present and uncommented in inetd.conf
  4. Verify statd network listening status
    Run `netstat -an | grep 111` or `sockstat | grep statd` to check if statd is listening on network ports
    Affected if The statd daemon is bound to network interfaces (0.0.0.0 or ::)

A system is affected if it runs Solaris 8, 9, 10, or 11 Express AND has the statd daemon enabled and running, exposing the vulnerable service to network 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle critical patch updates for the affected Solaris versions. If patches are unavailable for end-of-life versions, consider upgrading to a supported Solaris release or disabling statd if not required for NFS operations.

Fix this in Solaris Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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