Seil Plus FirmwareOperating system · Iij

CVE-2014-7256

HIGH · 7.8 CVSS v2.0 Published 2014-12-05
Fix available
A fix is available. Upgrade to after 4.61 or later.
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 (1) PPP Access Concentrator (PPPAC) and (2) Dial-Up Networking Internet Initiative Japan Inc. SEIL series routers SEIL/x86 Fuji 1.00 through 3.22; SEIL/X1, SEIL/X2, and SEIL/B1 1.00 through 4.62; SEIL/Turbo 1.82 through 2.18; and SEIL/neu 2FE Plus 1.82 through 2.18 allow remote attackers to cause a denial of service (restart) via crafted (a) GRE or (b) MPPE packets.

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

SEIL series routers and PPPAC devices contain a vulnerability in their handling of GRE and MPPE packets. Remote attackers can send specially crafted packets causing the device to restart, resulting in denial of service. The vulnerability affects multiple firmware versions across several router models.

MitigationApply vendor patches from Internet Initiative Japan Inc. for the affected firmware versions. If patches are unavailable, implement network-level filtering for unusual GRE/MPPE traffic patterns or isolate affected devices behind additional security controls.

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
Seil Plus FirmwareOperating system
Affected:= 1.82= 1.83= 1.84= 1.85= 1.86= 1.87= 1.88= 1.89= 1.90= 1.91= 1.92= 1.93
Seil PlusHardware / appliance
Affected:all versions
Seil B1 FirmwareOperating system
Affected:<= 4.61
Seil X1 FirmwareOperating system
Affected:<= 4.61
Seil Turbo FirmwareOperating system
Affected:= 1.82= 1.83= 1.84= 1.85= 1.86= 1.87= 1.88= 1.89= 1.90= 1.91= 1.92= 1.93
Seil TurboHardware / appliance
Affected:all versions
Seil X86 Fuji FirmwareOperating system
Affected:<= 3.21
Seil X2 FirmwareOperating system
Affected:<= 4.61

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 SEIL router model
    Log into the router administrative interface or check hardware labeling to determine the exact SEIL model (Plus, Plus Firmware, B1, X1, Turbo, X86 Fuji, or X2).
    Affected if The model is any of: Iij Seil Plus, Iij Seil B1, Iij Seil X1, Iij Seil Turbo, Iij Seil X86 Fuji, or Iij Seil X2.
  2. Check firmware version
    Access router CLI or web interface and retrieve the firmware version (typically via 'show version' command or system status page). Compare against affected ranges: Seil Plus/B1/X1/Turbo/X2 firmware <=4.61, Seil Plus/Turbo (non-firmware) all versions, Seil X86 Fuji <=3.21, Seil Plus/Turbo firmware specific versions 1.82-1.93.
    Affected if Firmware version falls within or below the affected ranges listed for your specific model.
  3. Verify GRE protocol configuration
    Check router configuration for GRE tunnel interfaces or passthrough settings (look for 'gre', 'tunnel', or 'proxy-gre' in running config or web interface under interface or tunnel settings).
    Affected if GRE protocol is enabled or configured on the device.
  4. Verify MPPE configuration
    Check router configuration for MPPE (Microsoft Point-to-Point Encryption) settings, typically found in VPN or PPP configuration sections (look for 'mppe', 'pptp', or 'vpn' settings).
    Affected if MPPE encryption or PPTP VPN with MPPE is enabled.

A defender is affected if they run any SEIL router model with firmware matching the affected versions AND have GRE or MPPE protocols enabled in their configuration.

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

Apply vendor patches from Internet Initiative Japan Inc. for the affected firmware versions. If patches are unavailable, implement network-level filtering for unusual GRE/MPPE traffic patterns or isolate affected devices behind additional security controls.

Fix this in Seil Plus Firmware 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 the upgrade done

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-2014-7256 — 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-2014-7256 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