OA 2017: Allocation of Resources Without Limits or Throttling
CVE-2024-10599 is a high-severity allocation of resources without limits or throttling vulnerability in OA 2017 from Tongda, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected OA 2017 versions: 11.0; 11.1; 11.2, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1% chance of exploitation within 30 days, higher than 64% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of OA 2017 you run against the affected versions below, and install the vendor's latest release.
- 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 |
|---|---|---|---|
| Tongda | OA 2017 | 11.0; 11.1; 11.2; 11.3; 11.4; 11.5; 11.6; 11.7 | Not stated |
| Tongda2000 | Office Anywhere | 11.0 through 11.7; 2017 | Not stated |
Version data comes from the organisation that assigned the CVE. 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
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 6.9 | Medium | CNA (vuldb.com) |
| CVSS 3.1 | 5.3 | Medium | CNA (vuldb.com) |
| CVSS 3.1 | 7.5 | High | NVD |
| CVSS 2.0 | 5.0 | Medium | CNA (vuldb.com) |
Official description
A vulnerability, which was classified as problematic, has been found in Tongda OA 2017 up to 11.7. This issue affects some unknown processing of the file /inc/package_static_resources.php. The manipulation leads to resource consumption. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Allocation of Resources Without Limits or Throttling
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
How developers prevent this class of flaw
- Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
- Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
More Allocation of Resources Without Limits or Throttling vulnerabilities (CWE-770)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- vuldb.com/?id.282611Third Party Advisory, VDB Entry
- vuldb.com/?submit.433496Third Party Advisory, VDB Entry
Technical write-ups (may include proof of concept)
- github.com/LvZCh/td/issues/2Exploit, Third Party Advisory
Other references
- vuldb.com/?ctiid.282611Permissions Required, VDB Entry
Other vulnerabilities in OA 2017
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
Recent Allocation of Resources Without Limits or Throttling vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 9.1 Critical severity
- 7.5 High severity
- 8.7 High severity
Spotted an error? Tell us.