dbcve.org
Fibeair Ip 10 FirmwareOperating system · Ceragon

CVE-2016-10309

CRITICAL · 9.8 CVSS v3.0 Published 2017-03-30
Fix available
A fix is available. Upgrade to after 7.1.0 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
In the GUI of Ceragon FibeAir IP-10 (before 7.2.0) devices, a remote attacker can bypass authentication by adding an ALBATROSS cookie with the value 0-4-11 to their browser.

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 Ceragon FibeAir IP-10 device web GUI (versions before 7.2.0) contains an authentication bypass vulnerability where remote attackers can gain unauthorized access by adding an ALBATROSS cookie with value 0-4-11 to HTTP requests. This allows complete bypass of the authentication mechanism without needing valid credentials.

MitigationUpgrade Ceragon FibeAir IP-10 devices to firmware version 7.2.0 or later to patch the authentication bypass. If immediate patching is not possible, restrict network access to the management interface using firewalls or ACLs.

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
Fibeair Ip 10 FirmwareOperating system
Affected:<= 7.1.0

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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
    Access the device's web GUI or CLI and locate the system information or device status page to confirm it is a Ceragon FibeAir IP-10 device
    Affected if The device is not a Ceragon FibeAir IP-10 model
  2. Check the firmware version
    In the device web GUI, navigate to the System or Management section to view the firmware version. Alternatively, access the CLI and run the command to display firmware version (typically 'show version' or similar)
    Affected if The firmware version is 7.1.0 or earlier (any version below 7.2.0)
  3. Verify web GUI is network-accessible
    Attempt to access the device's web interface over HTTP/HTTPS from a remote system, or check firewall rules and network ACLs to determine if the management port (typically 80 or 443) is exposed to untrusted networks
    Affected if The web management interface is accessible from networks outside the trusted management network
  4. Test cookie-based authentication bypass
    Send an HTTP request to the device login page or any protected page with a cookie named 'ALBATROSS' set to the value '0-4-11'. Check if the response grants access or returns authenticated content without providing valid credentials
    Affected if The device grants access when the ALBATROSS cookie is set to '0-4-11', indicating the authentication bypass is present

You are affected if your Ceragon FibeAir IP-10 device runs firmware version 7.1.0 or earlier and the web GUI is accessible, since the ALBATROSS cookie value 0-4-11 can bypass authentication in these versions.

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 7.1.0
Interim mitigation

Upgrade Ceragon FibeAir IP-10 devices to firmware version 7.2.0 or later to patch the authentication bypass. If immediate patching is not possible, restrict network access to the management interface using firewalls or ACLs.

Recommended fix High confidence

Firmware 7.2.0 or later

  1. Identify the specific FibeAir IP-10 device model and current firmware version
  2. Obtain firmware version 7.2.0 or later from Ceragon's official support portal or vendor
  3. Backup the current device configuration through the web GUI or CLI
  4. Access the device's web interface and navigate to the firmware upgrade section
  5. Upload and install the new firmware version 7.2.0 or later
  6. Allow the device to reboot and complete the upgrade process
  7. Verify the device is running the new firmware version
  8. Confirm the authentication bypass vulnerability is no longer present by attempting the ALBATROSS cookie attack
Caveat Check Ceragon release notes for any configuration or feature changes between 7.1.0 and 7.2.0

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

Fix this in Fibeair Ip 10 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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