CVE-2023-6198
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 Baicells Snap Router BaiCE_BMI on EP3011 (User Passwords modules) allows unauthorized access to the 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 confidenceHardcoded credentials vulnerability in the User Passwords module of Baicells Snap Router BaiCE_BMI (EP3011) allows unauthorized attackers to gain access to the device using predetermined credentials that are embedded in the firmware and cannot be changed through normal configuration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:L
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 device model and firmware versionAccess the device administrative interface or check the device label for model number EP3011 or Baicells Snap Router BaiCE_BMI. Look for firmware version in system settings or startup logs.Affected if Device is Baicells Snap Router BaiCE_BMI (EP3011)
-
Verify User Passwords module accessibilityLocate the User Passwords or User Management section in the device web interface or CLI. Confirm whether this module is present and accessible.Affected if User Passwords module exists and is accessible on the device
-
Test credential change capabilityAttempt to change the admin or user passwords through the User Passwords module interface. Note whether the change operation succeeds and whether the new credentials persist after reboot.Affected if Password changes cannot be saved, do not persist, or the interface shows the credentials are hardcoded/unmodifiable
-
Check for default credential exposureReview any documentation, default password lists, or attempt known common default credentials for Baicells devices. Check if the device responds to authentication with well-known default credentials.Affected if Device accepts authentication with default or publicly documented credentials
-
Inspect firmware for embedded credentialsIf firmware analysis is possible, extract firmware filesystem and search for hardcoded password strings or credential patterns in configuration files.Affected if Firmware contains plaintext or encoded hardcoded credentials that cannot be modified
You are affected if the device is a Baicells Snap Router BaiCE_BMI (EP3011) with a User Passwords module containing credentials that cannot be changed through normal configuration or accept known default values.
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 dataImmediately change any default credentials; if hardcoded credentials cannot be modified through the administrative interface, isolate the device behind a firewall or disable remote management, and contact the vendor for a firmware update that removes the hardcoded credentials.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6198 — 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-6198 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