dbcve.org
Cfr 1004ea FirmwareOperating system · C First

CVE-2023-47674

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-16
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
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
Missing authentication for critical function vulnerability in First Corporation's DVRs allows a remote unauthenticated attacker to rewrite or obtain the configuration information of the affected device. Note that updates are provided only for Late model of CFR-4EABC, CFR-4EAB, CFR-8EAB, CFR-16EAB, MD-404AB, and MD-808AB. As for the other products, apply the workaround.

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

Missing authentication bypass vulnerability in First Corporation DVRs allows remote unauthenticated attackers to access critical configuration functions, enabling both reading and modification of device settings without any credentials.

MitigationApply vendor-supplied firmware updates to affected models (CFR-4EABC, CFR-4EAB, CFR-8EAB, CFR-16EAB, MD-404AB, MD-808AB); for unpatched models, implement network segmentation and restrict management interface exposure to trusted networks.

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
Cfr 1004ea FirmwareOperating system
Affected:all versions
Cfr 1008ea FirmwareOperating system
Affected:all versions
Cfr 1016ea FirmwareOperating system
Affected:all versions
Cfr 16eaa FirmwareOperating system
Affected:all versions
Cfr 16eab FirmwareOperating system
Affected:all versions
Cfr 16eha FirmwareOperating system
Affected:all versions
Cfr 16ehd FirmwareOperating system
Affected:all versions
Cfr 4eaa 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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the DVR model number
    Check the device label, web interface login page, or system information page for the model designation (e.g., CFR-1004ea, CFR-1008ea, CFR-1016ea, CFR-16eaa, CFR-16eab, CFR-16eha, CFR-16ehd, CFR-4eaa)
    Affected if The model matches any of the CFR-xxxxea variants listed in the affected products
  2. Check the firmware version
    Access the DVR system settings or about page via the web interface to view the installed firmware version
    Affected if The device is a First Corporation CFR model and runs any firmware version (all versions are affected)
  3. Determine network exposure of the management interface
    Check firewall rules, router configuration, or network ACLs to see if the DVR web interface (typically ports 80/443 or custom ports) is accessible from external/untrusted networks
    Affected if The management interface is exposed to the internet or untrusted networks without VPN or IP restrictions
  4. Test critical configuration endpoints for authentication bypass
    Send HTTP requests to configuration endpoints (such as /config, /settings, or API paths for device configuration) without providing any credentials and observe if access is granted
    Affected if Unauthenticated requests to critical configuration functions return valid responses or allow access to device settings

The environment is affected if a First Corporation CFR-series DVR (any firmware version) has its management interface exposed to untrusted networks and critical configuration endpoints are accessible without authentication.

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

Apply vendor-supplied firmware updates to affected models (CFR-4EABC, CFR-4EAB, CFR-8EAB, CFR-16EAB, MD-404AB, MD-808AB); for unpatched models, implement network segmentation and restrict management interface exposure to trusted networks.

Recommended fix Moderate confidence

Late model firmware for CFR-4EABC, CFR-4EAB, CFR-8EAB, CFR-16EAB, MD-404AB, MD-808AB (specific version numbers not specified in advisory)

  1. 1. Identify the specific model of the CFR series DVR device from the affected product list
  2. 2. For models CFR-4EABC, CFR-4EAB, CFR-8EAB, CFR-16EAB, MD-404AB, and MD-808AB: Check First Corporation's official support website (www.c-first.co.jp) for firmware updates labeled as 'Late model' and apply the latest available firmware update
  3. 3. For all other affected models (CFR-1004ea, CFR-1008ea, CFR-1016ea, CFR-16eaa, CFR-16eab, CFR-16eha, CFR-16ehd, CFR-4eaa): Apply workaround: ensure the device is not directly exposed to the internet by placing it behind a properly configured firewall or NAT, and restrict network access to only trusted IP addresses
  4. 4. After applying firmware update or workaround, verify the device configuration cannot be accessed without authentication by attempting unauthorized access from an untrusted network segment

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

Fix this in Cfr 1004ea Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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