cbcvebase.
CVE-2023-6329
published 2023-11-27

CVE-2023-6329: An authentication bypass vulnerability exists in Control iD iDSecure v4.7.32.0. The login routine used by iDS-Core.dll contains a "passwordCustom" option that…

PriorityP190critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
ITWEXPLOITVulnCheck KEVInitial access
Exploited in the wild
EPSS
65.24%
99.2th percentile
An authentication bypass vulnerability exists in Control iD iDSecure v4.7.32.0. The login routine used by iDS-Core.dll contains a "passwordCustom" option that allows an unauthenticated attacker to compute valid credentials that can be used to bypass authentication and act as an administrative user.

Affected

2 ranges
VendorProductVersion rangeFixed in
control_ididsecure
controlididsecure

Detection & IOCsextracted from sources · hover to see the quote

url/api/login/unlockGetData
url/api/login/
url/api/operator/
otherpasswordCustom
other{"passwordCustom": "<computed>", "passwordRandom": "<random>"}
othercid2016
filenameiDS-Core.dll
  • Detect unauthenticated GET requests to /api/login/unlockGetData followed by a POST to /api/login/ containing the 'passwordCustom' JSON field — this is the two-step authentication bypass sequence.
  • Flag POST requests to /api/login/ whose JSON body contains the key 'passwordCustom' without a standard password field — this indicates exploitation of the bypass.
  • Alert on POST requests to /api/operator/ bearing a Bearer token obtained without prior authenticated login, especially when the body contains 'idType', 'newPassword', and 'password_confirmation' — this indicates new admin account creation post-bypass.
  • Monitor HTTP responses from /api/login/ for the presence of 'accessToken' in the JSON body following a passwordCustom login attempt — this confirms successful authentication bypass.
  • Use FOFA/Shodan/Censys query body="iDSecure" to identify exposed iDSecure instances for proactive asset discovery and patching prioritization.
  • The credential computation uses a hardcoded salt string 'cid2016' combined with a SHA-1 of the device serial and a random numeric string, then SHA-256 hashed; presence of this pattern in traffic or logs is a strong exploit indicator.
  • Successful exploitation results in a response containing both 'code' and 'newID' fields in the /api/operator/ response body — monitor for these fields to detect new admin account creation.
  • ·The vulnerability affects Control iD iDSecure versions up to and including v4.7.43.0, not just v4.7.32.0 as stated in the NVD entry.
  • ·The bypass relies on the device's serial number retrieved unauthenticated from /api/login/unlockGetData; if this endpoint is firewalled or rate-limited, exploitation is blocked at the first step.
  • ·The passwordCustom value is derived from the first 6 hex characters of a SHA-256 hash converted to a decimal integer — detection logic must account for this numeric string format rather than a fixed credential.

CVSS provenance

nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vulncheck9.8CRITICAL
CVEs like this are exactly what “Exploited This Week” covers.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.