CVE-2023-47213
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 · uneditedFirst Corporation's DVRs use a hard-coded password, which may allow 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 · moderate confidenceFirst Corporation DVR devices contain a hard-coded password vulnerability that allows remote unauthenticated attackers to access configuration settings. An attacker with network access to the affected device can read or modify the device configuration without credentials.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 the DVR device modelAccess the device web interface or check the physical device label for the model number. Common access methods: navigate to the login page and look for model information in the footer, or check System Information page under Settings.Affected if The model number matches any of the following: C First Cfr 1004ea, C First Cfr 1008ea, C First Cfr 1016ea, C First Cfr 16eaa, C First Cfr 16eab, C First Cfr 16eha, C First Cfr 16ehd, or C First Cfr 4eaa
-
Confirm firmware versionLog into the device web interface and navigate to System > Information or Settings > Device Info to view the installed firmware version.Affected if Any firmware version is installed on an affected model listed above (all versions are vulnerable)
-
Check if remote network access is enabledAccess the device network settings: go to Settings > Network or System > Network Configuration. Look for options such as 'Remote Access', 'Cloud Service', 'P2P', 'DDNS', or 'Port Forwarding' that allow external network connections.Affected if Remote access, cloud connectivity, P2P, or any external network management feature is enabled and exposed to untrusted networks
-
Verify if default credentials provide accessAttempt to log into the device web interface using common default credentials (such as admin/admin, admin/123456, or empty password). The hardcoded password is present in all affected firmware versions.Affected if Default or known hardcoded credentials successfully authenticate to the device, indicating the vulnerability is present and exploitable
The environment is affected if the device is any First Corporation CFR model listed and remote network access is enabled, allowing unauthenticated attackers to access configuration using the hardcoded password.
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.
From vendor dataUpdate to patched firmware versions for supported models (CFR-4EABC, CFR-4EAB, CFR-8EAB, CFR-16EAB, MD-404AB, MD-808AB). For unsupported models, implement vendor-provided workarounds such as network segmentation or disabling remote access.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47213 — 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-2023-47213 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