dbcve.org
NetbsdOperating system

CVE-2008-1335

HIGH · 9.3 CVSS v2.0 Published 2008-03-13
Fix available
A fix is available. Upgrade to after 20071027 or later.
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
The ipsec4_get_ulp function in the kernel in NetBSD 2.0 through 3.1 and NetBSD-current before 20071028, when the fast_ipsec subsystem is enabled, allows remote attackers to bypass the IPsec policy by sending packets from a source machine with a different endianness than the destination machine, a different vulnerability than CVE-2006-0905.

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

The ipsec4_get_ulp function in the NetBSD kernel (versions 2.0-3.1 and NetBSD-current before 20071028) contains a flaw in the fast_ipsec subsystem that allows remote attackers to bypass IPsec policy enforcement by exploiting endianness differences between source and destination machines.

MitigationDisable the fast_ipsec subsystem if possible, or upgrade to NetBSD 3.1.1 or later/NetBSD-current after 20071028 which contains the patch. Alternatively, ensure network architecture prevents untrusted external machines with different endianness from reaching the IPsec-protected network.

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
NetbsdOperating system
Affected:= 2.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 2.1= 2.1.1= 3.0= 3.0.1= 3.0.2= 3.1
Netbsd CurrentOperating system
Affected:<= 20071027

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

AV:N/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. Identify NetBSD version
    Run 'uname -a' or check /etc/release to see the installed NetBSD version number (e.g., 2.0, 2.1, 3.0, 3.1)
    Affected if The version is 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.1, 2.1.1, 3.0, 3.0.1, 3.0.2, or 3.1, or it is NetBSD-current dated 20071027 or earlier
  2. Determine if fast_ipsec is in use
    Check kernel configuration files or running kernel for fast_ipsec module: look for 'fast_ipsec' in kernel config, check 'modstat' output for loaded IPsec modules, or inspect kernel boot messages for fast_ipsec initialization
    Affected if The fast_ipsec subsystem (fast_ipsec) is compiled into or loaded by the running kernel
  3. Verify IPsec policy enforcement is active
    Examine IPsec policy configuration using 'setkey -DP' or check /etc/ipsec.conf for defined security policies
    Affected if IPsec policies are configured and the system is relying on them for network access control

You are affected if you run NetBSD 2.0-3.1 or NetBSD-current up to 20071027 with the fast_ipsec subsystem enabled and depend on IPsec policy enforcement for access control.

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
Upgrade available Upgrade to a release after 20071027
Interim mitigation

Disable the fast_ipsec subsystem if possible, or upgrade to NetBSD 3.1.1 or later/NetBSD-current after 20071028 which contains the patch. Alternatively, ensure network architecture prevents untrusted external machines with different endianness from reaching the IPsec-protected network.

Recommended fix Moderate confidence

NetBSD 3.1 or later, or NetBSD-current dated after 20071028

  1. 1. Identify the current NetBSD version by running 'uname -a' or 'sysctl kern.version'
  2. 2. Back up all critical data and configuration files before upgrading
  3. 3. Obtain the fixed NetBSD release (3.1 or later) from the official NetBSD releases: https://cdn.netbsd.org/pub/NetBSD/NetBSD-release-3_1/ or https://cdn.netbsd.org/pub/NetBSD/NetBSD-current/
  4. 4. Follow the NetBSD upgrade guide at https://www.netbsd.org/docs/upgrading.html to perform a system upgrade
  5. 5. After upgrading, verify the kernel version includes the fix by checking 'sysctl kern.version' for dates after 20071028
  6. 6. If using fast_ipsec, verify IPsec policies are working correctly with 'ipsecctl -s all'
  7. 7. Test that IPsec policy enforcement is functioning as expected
Caveat Upgrading NetBSD kernel may require rebuilding third-party kernel modules; ensure compatibility with installed packages

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

Fix this in Netbsd Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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