Data OntapOperating system · Netapp

CVE-2008-3349

HIGH · 10.0 CVSS v2.0 Published 2008-07-28
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
Multiple unspecified vulnerabilities in NetApp Data ONTAP, as used on NetApp and IBM eServer platforms, allow remote attackers to execute arbitrary commands, cause a denial of service (system crash), or obtain sensitive information, probably related to insufficient access control for HTTP requests. NOTE: this may overlap CVE-2008-3160.

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

Multiple critical vulnerabilities in NetApp Data ONTAP allow remote unauthenticated attackers to execute arbitrary commands, cause system crashes, or obtain sensitive information through insufficient access control on HTTP requests. The CVSS 10 score indicates trivial network access with no authentication required yields complete system compromise.

MitigationImmediately restrict or disable HTTP management access if not required, and apply vendor patches for Data ONTAP to address the authentication bypass vulnerabilities. If the affected systems cannot be patched immediately, network segment the storage infrastructure and monitor for exploitation attempts.

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
Data OntapOperating system
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
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/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. Confirm NetApp Data ONTAP is installed
    Identify if the system is a NetApp storage array running Data ONTAP. Check system documentation, hardware identification, or log into the storage controller to verify the operating system.
    Affected if The system is running NetApp Data ONTAP (all versions are affected)
  2. Determine if HTTP management interface is enabled
    Check the Data ONTAP configuration for HTTP/HTTPS management access. In Data ONTAP, this is typically controlled via the 'httpd' or 'options http' settings. Use the command 'options http' or 'httpd' from the storage console to see if HTTP management is enabled.
    Affected if HTTP management interface is enabled on the Data ONTAP device
  3. Check network exposure of management interfaces
    Determine if the HTTP port (usually port 80 or 443) used for Data ONTAP management is accessible from untrusted networks. Scan external-facing network interfaces or review firewall rules to see if port 80/443 is open to the internet or untrusted VLANs.
    Affected if The HTTP management port is exposed to untrusted network segments or the internet
  4. Review authentication configuration
    Examine the Data ONTAP 'options trusted.hosts' and authentication settings to verify whether the system is configured to allow unauthenticated HTTP requests. Check if IP-based access controls are properly configured.
    Affected if Trusted hosts are not configured or unauthenticated HTTP requests are permitted

If the system runs NetApp Data ONTAP with HTTP management enabled and exposed to untrusted networks, it is affected by CVE-2008-3349 and vulnerable to unauthenticated command execution.

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

Immediately restrict or disable HTTP management access if not required, and apply vendor patches for Data ONTAP to address the authentication bypass vulnerabilities. If the affected systems cannot be patched immediately, network segment the storage infrastructure and monitor for exploitation attempts.

Fix this in Data Ontap Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-3349 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2008-3349 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