CVE-2024-22074
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 · uneditedDynamsoft Service 1.8.1025 through 1.8.2013, 1.7.0330 through 1.7.2531, 1.6.0428 through 1.6.1112, 1.5.0625 through 1.5.3116, 1.4.0618 through 1.4.1230, and 1.0.516 through 1.3.0115 has Incorrect Access Control. This is fixed in 1.8.2014, 1.7.4212, 1.6.3212, 1.5.31212, 1.4.3212, and 1.3.3212.
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 · moderate confidenceDynamsoft Service contains an incorrect access control vulnerability that allows unauthenticated remote attackers to potentially bypass security restrictions and gain unauthorized access to sensitive functionality or data. The critical severity (CVSS 9.8) indicates trivial exploitability with no user interaction required.
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>= 1.0.516, < 1.3.3212>= 1.4.1230, < 1.4.3212>= 1.5.0625, < 1.5.31212>= 1.6.0428, < 1.6.3212>= 1.7.0330, < 1.7.4212>= 1.8.1025, < 1.8.2014CVSS 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.
-
Check if Dynamsoft Service is installedOpen Windows Services console (services.msc) and look for a service named 'Dynamsoft Service' or search for 'Dynamsoft' in Program Files directory (C:\Program Files\Dynamsoft or C:\Program Files (x86)\Dynamsoft)Affected if The service or Dynamsoft installation folder is present on the system
-
Identify the installed versionRight-click the Dynamsoft Service in Services console, go to Properties, and check the 'Path to executable' to locate the service binary. Then right-click the .exe file in File Explorer, select Properties, and view the Version tab for the File VersionAffected if The version number displayed is within any of the vulnerable ranges: >=1.0.516 and <1.3.3212, >=1.4.1230 and <1.4.3212, >=1.5.0625 and <1.5.31212, >=1.6.0428 and <1.6.3212, >=1.7.0330 and <1.7.4212, or >=1.8.1025 and <1.8.2014
-
Check service network exposureOpen Command Prompt and run 'netstat -an | findstr LISTENING' to list listening ports. Dynamsoft Service typically exposes ports 18622 or 18623. Also check firewall rules with 'netsh advfirewall firewall show rule name=all' for Dynamsoft-related inbound rulesAffected if The service is listening on network ports and accessible from network hosts (especially if no firewall rule blocks external access)
-
Verify service is running with elevated privilegesIn Services console, double-click the Dynamsoft Service and check the 'Log on as' setting. The vulnerability allows privilege escalation due to incorrect access control, so note if the service runs as LocalSystem or another privileged accountAffected if The service runs with elevated privileges (especially LocalSystem) and is network-accessible to unauthenticated users
If Dynamsoft Service is installed and its version falls within any of the affected ranges listed above, and the service is exposed on the network, the environment is vulnerable to CVE-2024-22074.
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.
dbcve · scoped1.3.32121.4.32121.5.31212
Upgrade Dynamsoft Service to version 1.8.2014, 1.7.4212, 1.6.3212, 1.5.31212, 1.4.3212, or 1.3.3212 or later. Given the critical severity and likely network-exploitable nature, prioritize patching for all exposed instances.
Upgrade to version 1.3.3212 (for 1.0.x-1.3.x), 1.4.3212 (for 1.4.x), 1.5.31212 (for 1.5.x), 1.6.3212 (for 1.6.x), 1.7.4212 (for 1.7.x), or 1.8.2014 (for 1.8.x) - choose the version matching your major release line
- Identify the currently installed Dynamsoft Service version using the service control panel or system inventory
- Determine which major version line (1.3.x, 1.4.x, 1.5.x, 1.6.x, 1.7.x, or 1.8.x) the current installation belongs to
- Download the appropriate fixed version for that major version line from the official Dynamsoft website (www.dynamsoft.com)
- Stop the Dynamsoft Service through Windows Services or the command 'net stop Dynamsoft Service'
- Install the downloaded fixed version by running the installer with elevated (administrator) privileges
- Verify the installation completed successfully and the service is running
- Confirm the installed version matches the expected fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22074 — 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-2024-22074 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