dbcve.org
Control Id IdsecureApplication · Assaabloy

CVE-2023-33370

HIGH · 7.5 CVSS v3.1 Published 2023-08-03
Fix available
A fix is available. Upgrade to after 4.7.26.0 or later.
See remediation →
84/100
Remediation priority · High
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
An uncaught exception vulnerability exists in Control ID IDSecure 4.7.26.0 and prior, allowing attackers to cause the main web server of IDSecure to fault and crash, causing a denial of service.

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

IDSecure 4.7.26.0 and prior versions contain an uncaught exception in the web server component that causes the application to fault and crash when triggered, resulting in denial of service. The vulnerability allows unauthenticated remote attackers to send specially crafted requests that trigger the unhandled exception.

MitigationUpgrade IDSecure to a version newer than 4.7.26.0 that includes proper exception handling. If patching is not immediately possible, consider network segmentation to limit exposure to untrusted networks.

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 IdsecureApplication
Affected:<= 4.7.26.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Determine installed IDSecure version
    Open the IDSecure application and navigate to Help > About, or check the Windows Programs and Features list for the installed version number
    Affected if The displayed version is 4.7.26.0 or lower
  2. Confirm web server component is running
    Check the IDSecure service status or look for the web server process in Task Manager; the vulnerability exists in the web server component
    Affected if The web server component is active or the associated service is running
  3. Verify network exposure of IDSecure web interface
    Check if the IDSecure web server port (commonly 8080 or 8443) is listening on external network interfaces or accessible from untrusted networks
    Affected if The web interface is reachable from networks outside the trusted internal network

You are affected if IDSecure version 4.7.26.0 or lower is installed with the web server component enabled and exposed to network access.

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
Upgrade available Upgrade to a release after 4.7.26.0
Interim mitigation

Upgrade IDSecure to a version newer than 4.7.26.0 that includes proper exception handling. If patching is not immediately possible, consider network segmentation to limit exposure to untrusted networks.

Fix this in Control Id Idsecure Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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