dbcve.org
Firepass 1200Hardware / appliance · F5

CVE-2008-3149

HIGH · 7.8 CVSS v2.0 Published 2008-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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
The SNMP daemon in the F5 FirePass 1200 6.0.2 hotfix 3 allows remote attackers to cause a denial of service (daemon crash) by walking the hrSWInstalled OID branch in HOST-RESOURCES-MIB.

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

The SNMP daemon in F5 FirePass 1200 version 6.0.2 hotfix 3 crashes when an attacker walks the hrSWInstalled OID branch within the HOST-RESOURCES-MIB. This causes a denial of service condition, rendering the SNMP service unavailable.

MitigationRestrict or disable SNMP access to the FirePass device (e.g., via ACLs, firewall rules, or SNMP community string changes) to prevent unauthenticated remote attackers from triggering the crash. If available, apply vendor-supplied patches or firmware updates.

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
Firepass 1200Hardware / appliance
Affected:= 6.0.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
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:N/C:N/I:N/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. Identify the device model
    Log into the FirePass management interface (web UI or CLI) and navigate to System > Platform or use 'show system info' command to confirm the device is a F5 FirePass 1200
    Affected if The device is not a F5 FirePass 1200, then this CVE does not apply
  2. Check the firmware version
    In the web UI, go to System > Software or use 'show version' command via CLI. Confirm the exact installed version is 6.0.2
    Affected if The installed version is exactly 6.0.2 (any hotfix level), the device is vulnerable
  3. Verify SNMP is enabled
    In the web UI, navigate to System > Services > SNMP or check the SNMP configuration via CLI using 'show snmp' command
    Affected if SNMP is enabled and running, the service can be crashed via the malformed OID walk
  4. Check SNMP network exposure
    Review access control lists, firewall rules, or SNMP community string configuration to determine if SNMP port 161/162 is accessible from untrusted networks
    Affected if SNMP is exposed to network attackers, the DoS can be triggered remotely

You are affected if you have a F5 FirePass 1200 running firmware version 6.0.2 with SNMP enabled and accessible to potential 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

Restrict or disable SNMP access to the FirePass device (e.g., via ACLs, firewall rules, or SNMP community string changes) to prevent unauthenticated remote attackers from triggering the crash. If available, apply vendor-supplied patches or firmware updates.

Fix this in Firepass 1200 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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