dbcve.org
Colibri FirmwareOperating system · Franklinfueling

CVE-2023-5885

MEDIUM · 6.5 CVSS v3.1 Published 2023-11-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 discontinued FFS Colibri product allows a remote user to access files on the system including files containing login credentials for other users.

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 discontinued FFS Colibri product contains a vulnerability allowing remote unauthenticated users to access arbitrary files on the system via the web interface, including files containing login credentials for other users.

MitigationSince the product is discontinued and no patch is available, organizations should immediately cease use of FFS Colibri or implement strict network isolation/firewalling to block external access to the affected system.

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
Colibri FirmwareOperating system
Affected:all versions

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

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

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 Colibri system presence
    Locate the FFS Colibri fuel management system on the network by checking device inventory, DNS records, or by scanning for the Colibri web interface (typically on ports 80/443 or custom ports).
    Affected if The system is identified as a Franklin Fueling Systems Colibri fuel management controller.
  2. Verify web interface accessibility
    Attempt to access the Colibri web interface via HTTP/HTTPS from a network location. Look for the Colibri login page or any web-based fuel system interface.
    Affected if The web interface is reachable and responds, indicating the service is running and exposed.
  3. Confirm firmware version
    Access the web interface and check the firmware version information typically found in system settings, about page, or device status. If unable to access the interface, check network documentation or the device itself for firmware version details.
    Affected if The device is running any version of FFS Colibri firmware, as all versions are affected by this vulnerability.
  4. Assess network exposure
    Determine if the Colibri web interface is accessible from untrusted networks such as the internet or from network segments that contain untrusted users/systems. Review firewall rules and network ACLs applied to the device.
    Affected if The web interface is accessible from external/untrusted networks without proper network isolation or firewall filtering.

If the FFS Colibri system is present and its web interface is accessible (especially from untrusted networks), the environment is affected since all firmware versions contain this unauthenticated arbitrary file access vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the product is discontinued and no patch is available, organizations should immediately cease use of FFS Colibri or implement strict network isolation/firewalling to block external access to the affected system.

Recommended fix Moderate confidence
  1. 1. Review CISA advisory and Franklin Fueling security notifications for any available guidance
  2. 2. Since the Colibri product is discontinued and no patch is available, implement network segmentation to isolate the device
  3. 3. If the Colibri device must remain in service, place it behind a firewall with strict access controls
  4. 4. Monitor network traffic to and from the Colibri device for suspicious activity
  5. 5. Consider replacing the discontinued Colibri system with a supported alternative product from Franklin Fueling
  6. 6. Review all default credentials and change any stored credentials that may have been accessible through this vulnerability
  7. 7. Conduct a full security assessment of systems that were accessible from the Colibri device
Caveat Product is discontinued with no available security patch - replacement with a supported product recommended

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

Fix this in Colibri Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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