dbcve.org
Ac21000 G6 FirmwareOperating system · Connectize

CVE-2023-24047

MEDIUM · 6.8 CVSS v3.1 Published 2023-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
An Insecure Credential Management issue discovered in Connectize AC21000 G6 641.139.1.1256 allows attackers to gain escalated privileges via use of weak hashing algorithm.

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 confidence

The Connectize AC21000 G6 access point firmware version 641.139.1.1256 uses a weak hashing algorithm for storing credentials. Attackers who obtain password hashes (through other vulnerabilities or network access) can crack them more easily due to the weak algorithm, allowing privilege escalation to administrative levels.

MitigationUpgrade to a vendor-patched firmware version that implements strong password hashing (e.g., bcrypt, scrypt, or Argon2). After patching, enforce password changes for all user accounts to ensure previously compromised or weak hashes are replaced.

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
Ac21000 G6 FirmwareOperating system
Affected:= 641.139.1.1256

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
Adjacent
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:H/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. Check firmware version via web interface
    Log into the Connectize AC21000 G6 admin web interface. Navigate to Status, System, or About page where firmware version is displayed.
    Affected if The displayed firmware version is exactly 641.139.1.1256
  2. Check firmware version via CLI
    Access the device via SSH or console. Run commands such as 'show version', 'firmware version', or 'system info' to retrieve the firmware build number.
    Affected if The reported version matches 641.139.1.1256
  3. Check firmware version via SNMP
    If SNMP is enabled, query the device using OID for firmware version (commonly .1.3.6.1.2.1.1.1.0 or vendor-specific OIDs).
    Affected if The SNMP response returns 641.139.1.1256 as the firmware version

You are affected only if your Connectize AC21000 G6 is running firmware version 641.139.1.1256, which contains the weak password hashing algorithm.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a vendor-patched firmware version that implements strong password hashing (e.g., bcrypt, scrypt, or Argon2). After patching, enforce password changes for all user accounts to ensure previously compromised or weak hashes are replaced.

Fix this in Ac21000 G6 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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