dbcve.org
Ts 550 Evo FirmwareOperating system · Franklinfueling

CVE-2013-7248

HIGH · 10.0 CVSS v2.0 Published 2014-01-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
Franklin Fueling Systems TS-550 evo with firmware 2.0.0.6833 and other versions before 2.4.0 has a hardcoded password for the roleDiag account, which allows remote attackers to gain root privileges, as demonstrated using a cmdWebCheckRole action in a TSA_REQUEST.

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

Franklin Fueling Systems TS-550 evo console with firmware versions prior to 2.4.0 contains a hardcoded password for the roleDiag account, enabling remote attackers to authenticate and gain root privileges via the cmdWebCheckRole action in TSA_REQUEST.

MitigationUpgrade TS-500 evo firmware to version 2.4.0 or later to replace the hardcoded credential with a proper authentication mechanism; immediately change any default credentials if patching is delayed.

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
Ts 550 Evo FirmwareOperating system
Affected:= 2.0.0.6833= 2.3.1.7492
Ts 550 EvoHardware / appliance
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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/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. Confirm device model
    Identify if the target system is a Franklin Fueling Systems TS-550 evo console by checking the device label, web interface banner, or system information page
    Affected if The device is a Franklin Fueling Systems TS-550 evo console
  2. Check firmware version
    Access the console's admin or status page to view the installed firmware version number
    Affected if Firmware version is earlier than 2.4.0 or is specifically 2.0.0.6833 or 2.3.1.7492
  3. Verify web interface exposure
    Determine if the web management interface is accessible from the network by attempting to reach the device IP on common HTTP/HTTPS ports
    Affected if The web interface is externally accessible
  4. Identify hardcoded account presence
    Check if the roleDiag account exists in the user account list or authentication configuration of the TS-550 evo console
    Affected if The roleDiag account is present and uses a hardcoded password

You are affected if you have a TS-550 evo console running firmware versions before 2.4.0 with the roleDiag account accessible via the web interface.

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

Upgrade TS-500 evo firmware to version 2.4.0 or later to replace the hardcoded credential with a proper authentication mechanism; immediately change any default credentials if patching is delayed.

Recommended fix High confidence

Firmware version 2.4.0 or later

  1. Identify the current firmware version of the TS-550 evo console by accessing the device management interface
  2. Download firmware version 2.4.0 or later from Franklin Fueling Systems official support portal
  3. Review Franklin Fueling Systems upgrade documentation for any pre-upgrade requirements
  4. Backup current device configuration if supported by the system
  5. Upload and install firmware version 2.4.0 or later following the manufacturer's documented upgrade procedure
  6. After upgrade, verify the hardcoded credential vulnerability has been addressed by confirming the roleDiag account password has been changed or is no longer present
  7. Change any default credentials on the system following the upgrade to follow security best practices
Caveat Firmware upgrades on industrial control systems may require testing in a non-production environment first; verify compatibility with connected fuel dispensing equipment before deploying to production

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

Fix this in Ts 550 Evo Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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