Dynamsoft Service: Improper Access Control
CVE-2024-22074 is a critical-severity improper access control vulnerability in Dynamsoft Service from Dynamsoft, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 1.3.3212, 1.4.3212, 1.5.31212 as the first without the flaw, so updating Dynamsoft Service to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.45% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Dynamsoft Service to 1.3.3212 or 1.4.3212 or 1.5.31212 or 1.6.3212, whichever matches your release line, or a later version.
- Read the advisory on dynamsoft.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Dynamsoft | Dynamsoft Service | 1.0.516 up to, but not including, 1.3.3212; 1.4.1230 up to, but not including, 1.4.3212; 1.5.0625 up to, but not including, 1.5.31212; 1.6.0428 up to, but not including, 1.6.3212; 1.7.0330 up to, but not including, 1.7.4212; 1.8.1025 up to, but not including, 1.8.2014 | 1.3.3212, 1.4.3212, 1.5.31212, 1.6.3212, 1.7.4212, 1.8.2014 |
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | NVD |
| CVSS 3.1 | 9.8 | Critical | CISA (ADP) |
Official description
Dynamsoft 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Access Control
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Recent Improper Access Control vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 8.1 High severity
- 8.0 High severity
- 7.5 High severity
- 9.1 Critical severity
Spotted an error? Tell us.