Fortirecorder FirmwareOperating system · Fortinet
CVE-2019-6698
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 · uneditedUse of Hard-coded Credentials vulnerability in FortiRecorder all versions below 2.7.4 may allow an unauthenticated attacker with knowledge of the aforementioned credentials and network access to FortiCameras to take control of those, provided they are managed by a FortiRecorder device.
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 confidenceFortiRecorder versions below 2.7.4 contain hard-coded credentials that allow an unauthenticated attacker with network access to FortiCameras to take control of those cameras. The CVSS 9.8 indicates trivial exploitability with complete confidentiality, integrity, and availability impact.
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
Fortirecorder FirmwareOperating system
< 2.7.4CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify FortiRecorder installationLocate FortiRecorder by checking for FortiRecorder services, processes, or the FortiRecorder web interface in your environment. This may be on NVR (Network Video Recorder) hardware or as a virtual appliance.Affected if FortiRecorder software is present in the environment
-
Determine the firmware versionAccess the FortiRecorder CLI or web GUI and retrieve the firmware version. In the CLI, this is typically shown via 'get system status' or similar commands. The web interface usually displays the version on the dashboard or system info page.Affected if The installed firmware version is below 2.7.4
-
Verify network accessibility of management interfaceConfirm whether the FortiRecorder/FortiCamera management interface is reachable from network segments accessible to untrusted users. Check firewall rules, ACLs, or VLAN configurations that control access to port 80/443 or the management IP.Affected if The management interface is exposed to untrusted network segments (the hardcoded credentials can only be exploited if network access is possible)
You are affected if FortiRecorder is installed with firmware version below 2.7.4 and its management interface is network-accessible to untrusted users.
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.
dbcve · scoped2.7.4
Upgrade FortiRecorder to version 2.7.4 or later. If immediate patching is not feasible, restrict network access to the management interface using firewall rules or VLAN segmentation, and monitor for unauthorized access attempts.
FortiRecorder firmware 2.7.4 or later
- Obtain FortiRecorder firmware version 2.7.4 or later from the Fortinet support portal or official distribution channels
- Access the FortiRecorder management interface via web browser or console
- Navigate to the firmware upgrade section (typically under System > Firmware or similar)
- Upload the firmware image file (2.7.4 or later)
- Apply the firmware upgrade following the on-screen prompts
- Allow the device to reboot and complete the upgrade process
- Verify the firmware version has been updated to 2.7.4 or later
- After upgrade, change any default credentials and ensure network access controls are properly configured
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortirecorder Firmware
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6698 — 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-2019-6698 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