CVE-2023-41372
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 · uneditedThe vulnerability allows an unprivileged (untrusted) third- party application to arbitrary modify the server settings of the Android Client application, inducing it to connect to an attacker - controlled malicious server.This is possible by forging a valid broadcast intent encrypted with a hardcoded RSA key pair
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 confidenceAn Android Client application uses a hardcoded RSA key pair to encrypt broadcast intents, allowing any unprivileged third-party app to forge valid broadcast intents and modify the server settings to point to an attacker-controlled malicious server.
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 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model and firmwareIdentify the exact model number (WR2107, WR2110, or WR2115) and firmware version installed on the Ctrlx HMI Web PanelAffected if The device is any of these three models with any firmware version, as all versions are affected
-
Inspect application binary for hardcoded RSA keyAnalyze the Android application APK or application binaries for embedded RSA key material - look for static RSA private/public key pairs in code or configuration filesAffected if A hardcoded RSA key pair is found in the application, enabling encryption of forged intents
-
Verify broadcast receiver permission modelExamine the Android manifest and broadcast receiver implementation to determine if the receiver accepts intents without verifying the sender's identity or signatureAffected if The broadcast receiver accepts intents from any application without source verification or signature validation
-
Test intent injection capabilityFrom a separate (non-privileged) Android application, attempt to construct and send a broadcast intent with modified server settings using the known hardcoded RSA keyAffected if A third-party app can successfully modify server settings by sending forged broadcast intents, indicating the vulnerability is present and exploitable
The environment is affected if the device is a WR2107, WR2110, or WR2115 model running any firmware version and the application contains a hardcoded RSA key that allows third-party apps to forge broadcast intents to modify server settings.
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 dataRemove the hardcoded RSA key pair and implement proper cryptographic key management; add source verification to the broadcast receiver to ensure only trusted components can modify server settings.
- Consultation4.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41372 — 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-41372 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