dbcve.org
Control Id RhidApplication · Assaabloy

CVE-2023-2043

CRITICAL · 9.8 CVSS v3.1 Published 2023-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
A vulnerability, which was classified as problematic, was found in Control iD RHiD 23.3.19.0. This affects an unknown part of the file /v2/customerdb/operator.svc/a of the component Edit Handler. The manipulation of the argument email leads to sql injection. It is possible to initiate the attack remotely. The identifier VDB-225921 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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 confidence

SQL injection vulnerability in Control iD RHiD 23.3.19.0 allows remote attackers to inject malicious SQL queries via the email parameter in the /v2/customerdb/operator.svc/a endpoint (Edit Handler component). The critical CVSS 9.8 score indicates potential for complete compromise of the database.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in the Edit Handler component and implement strict input validation on the email parameter. Deploy a WAF rule as a temporary compensating control until the fix is implemented.

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
Control Id RhidApplication
Affected:= 23.3.19.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm installed product version
    Query the device web interface or check system information for the Assaabloy Control Id RHiD firmware/software version. Look for version 23.3.19.0 specifically in the about page, system status, or API version endpoint.
    Affected if The installed version is exactly 23.3.19.0
  2. Verify vulnerable endpoint is accessible
    Attempt to access or probe the URL path /v2/customerdb/operator.svc/a via HTTP/HTTPS on the device. This is a REST endpoint that should respond to requests.
    Affected if The endpoint returns a valid HTTP response (200, 400, 404, or similar) indicating the service is exposed and reachable
  3. Check if Edit Handler component is enabled
    Examine the web service configuration or API documentation for the device to determine if the Edit Handler component (operator.svc/a) is enabled and processing requests. This may be visible in the device management console or API documentation.
    Affected if The Edit Handler component is active and the /v2/customerdb/operator.svc/a endpoint processes requests with the email parameter
  4. Confirm external network exposure
    Review firewall rules, NAT configurations, or access control lists to determine if the web interface and /v2/ API endpoints are reachable from untrusted networks. Check if the device management interface is exposed to the internet.
    Affected if The vulnerable endpoint is reachable from external or untrusted networks

You are affected if you are running Control iD RHiD version 23.3.19.0 and the /v2/customerdb/operator.svc/a endpoint with the Edit Handler is accessible, regardless of network location.

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

Replace dynamic SQL queries with parameterized queries/prepared statements in the Edit Handler component and implement strict input validation on the email parameter. Deploy a WAF rule as a temporary compensating control until the fix is implemented.

Fix this in Control Id Rhid Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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