Server: Improper Authentication
CVE-2023-30223 is a high-severity improper authentication vulnerability in Server from 4D, 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 Server versions: 17; 18; 19. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.12% chance of exploitation within 30 days, higher than 67% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Server you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on blog.4d.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
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
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. Scored by NVD.
Official description
A broken authentication vulnerability in 4D SAS 4D Server software v17, v18, v19 R7, and earlier allows attackers to send crafted TCP packets containing requests to perform arbitrary actions.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How developers prevent this class of flaw
- Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- packetstormsecurity.comNot Applicable, Third Party Advisory, VDB Entry
Technical write-ups (may include proof of concept)
Other vulnerabilities in Server
- 7.5 High severity
- 7.8 High severity
- 7.5 High severity
Recent Improper Authentication vulnerabilities
- 3.9 Low severity
VMware Tools Authentication Bypass Exploited
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.1 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.