CVE-2015-5618
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 · uneditedChiyu BF-630 and BF-630W fingerprint access-control devices allow remote attackers to bypass authentication and (1) read or (2) modify (a) Voice Time Set configuration settings via a request to voice.htm or (b) UniFinger configuration settings via a request to bf.htm, a different vulnerability than CVE-2015-2871.
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 confidenceAuthentication bypass in Chiyu BF-630 and BF-630W fingerprint access-control devices allows unauthenticated remote attackers to read/modify Voice Time Set configuration via voice.htm and UniFinger configuration settings via bf.htm. The CVSS 7.5 indicates high exploitability with network-accessible attack vector and no privileges required.
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 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 device modelCheck the label, management interface, or HTTP response headers for the exact model number (BF-630 or BF-630W) from ChiyutwAffected if The device is a Chiyu BF-630 or BF-630W fingerprint access-control panel
-
Confirm firmware versionAccess the device web interface and navigate to the system or status page to view the firmware version informationAffected if The device runs any firmware version on the BF-630 or BF-630W (all versions are affected)
-
Check network exposure of the web interfaceDetermine if the device HTTP/HTTPS ports (typically 80/443) are reachable from untrusted networks or the public internet using nmap, curl, or network scanning toolsAffected if The administrative web interface is accessible from outside a trusted network
-
Test authentication on voice.htm endpointAttempt to access http://<device-ip>/voice.htm without providing credentials or login cookiesAffected if The page loads without requiring authentication, allowing unauthenticated access to Voice Time Set configuration
-
Test authentication on bf.htm endpointAttempt to access http://<device-ip>/bf.htm without providing credentials or login cookiesAffected if The page loads without requiring authentication, allowing unauthenticated access to UniFinger configuration settings
A user is affected if they have a Chiyu BF-630 or BF-630W device with its web interface network-accessible and the vulnerable endpoints (voice.htm, bf.htm) respond without authentication
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 dataIsolate affected devices behind a firewall or VLAN to limit exposure; contact Chiyu for firmware updates; if no patch exists, consider replacing with updated hardware. Implement monitoring for unauthorized access to administrative interfaces.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2015-5618 — 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-2015-5618 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