CVE-2023-3243
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** UNSUPPORTED WHEN ASSIGNED ** [An attacker can capture an authenticating hash and utilize it to create new sessions. The hash is also a poorly salted MD5 hash, which could result in a successful brute force password attack. Impacted product is BCM-WEB version 3.3.X. Recommended fix: Upgrade to a supported product such as Alerton ACM.] Out of an abundance of caution, this CVE ID is being assigned to better serve our customers and ensure all who are still running this product understand that the product is end of life and should be removed or upgraded.
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 confidenceBCM-WEB version 3.3.X allows an attacker to capture authentication hashes and reuse them to create new sessions. The authentication mechanism uses poorly salted MD5 hashes, making it vulnerable to brute force attacks to recover plaintext passwords.
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 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm BCM-WEB installationLocate the BCM-WEB application or device on your network. Check for Honeywell Alerton BCM Web servers, controllers, or management interfaces. Inspect network scans for HTTP services on ports typical for BCM-WEB (often port 80/443).Affected if BCM-WEB software or hardware is found in your environment
-
Identify the firmware versionAccess the BCM-WEB admin interface or check the device/system properties for the firmware version. Look for version information in the web UI header, system settings, or login page. Common paths: /about, /status, or the main login page often displays version info.Affected if The version number starts with 3.3 (such as 3.3.0, 3.3.1, 3.3.5, etc.)
-
Verify web authentication is enabledAttempt to access the BCM-WEB login page via HTTP/HTTPS. Confirm the authentication form is present and functional. Check if the login endpoint returns an authentication prompt.Affected if The web-based login interface is accessible and functional
-
Check network accessibilityDetermine if the BCM-WEB web interface is exposed to the network. Review firewall rules, VLAN configurations, and access control lists. Use port scanning (e.g., nmap) to identify exposed HTTP/HTTPS services.Affected if The BCM-WEB authentication portal is reachable from network segments beyond isolated management networks
Your environment is affected if BCM-WEB version 3.3.X is installed and its web authentication interface is accessible on your network.
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 dataUpgrade from the unsupported BCM-WEB 3.3.X to a supported product such as Alerton ACM, as no patches are available for this end-of-life product.
- Consultation12.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3243 — 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-3243 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