CVE-2005-3733
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 · uneditedThe Internet Key Exchange version 1 (IKEv1) implementation in Juniper JUNOS and JUNOSe software for M, T, and J-series routers before release 6.4, and E-series routers before 7-1-0, allows remote attackers to cause a denial of service and possibly execute arbitrary code via crafted IKE packets, as demonstrated by the PROTOS ISAKMP Test Suite for IKEv1. NOTE: due to the lack of details in the advisory, it is unclear which of CVE-2005-3666, CVE-2005-3667, and/or CVE-2005-3668 this issue applies to.
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 confidenceThe IKEv1 implementation in Juniper JUNOS and JUNOSe software for M, T, J-series routers (before 6.4) and E-series routers (before 7.1.0) contains a vulnerability that allows remote attackers to send crafted IKE packets causing denial of service and potentially arbitrary code execution, as demonstrated by the PROTOS ISAKMP Test Suite.
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<= 7.0.0<= 6.3<= 6.3<= 6.3<= 7.0.0<= 6.3<= 6.3.0<= 6.3CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed JUNOS/JUNOSe product versionAccess the router CLI and run the command to display the software version (such as 'show version' or 'show system software'). Compare the displayed version number against the affected ranges.Affected if The version is Junos E <= 7.0.0, Junos J <= 6.3, Junos M <= 6.3, Junos T <= 6.3, Junose E <= 7.0.0, Junose J <= 6.3, Junose M <= 6.3.0, or Junose T <= 6.3
-
Confirm the router seriesIdentify whether the device is an M-series, T-series, J-series, or E-series router using hardware inventory commands or model number display.Affected if The device is an M, T, J, or E series router running a version in the affected range from step 1
-
Verify IKEv1 is enabledCheck the IKE configuration on the router using commands to display security or VPN settings (such as 'show ike' or 'show security'). Determine if IKE Phase 1 negotiation is configured.Affected if IKEv1 is actively configured or enabled on the device, and the version falls within the affected ranges
The environment is affected if the router runs JUNOS or JUNOSe on M/T/J-series version 6.3 or earlier, or E-series version 7.0.0 or earlier, with IKEv1 enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade JUNOS/JUNOSe to version 6.4 or later for M/T/J-series, or 7.1.0 or later for E-series routers. If immediate upgrading is not feasible, consider filtering IKE traffic (UDP port 500) at network perimeter to block untrusted sources.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2005-3733 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2005-3733 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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