CVE-2023-1705 is a high severity (CVSS 8.4) missing authorization flaw in the Forcepoint F|ONE SmartEdge Agent on Windows. The bgAutoinstaller service modules allow privilege escalation and functionality bypass. Versions before 1.7.0.230330-554 are affected, so upgrade to that build or later.
What's affected
The NVD description says the issue affects Forcepoint F|ONE SmartEdge Agent before 1.7.0.230330-554. The vendor's knowledge base article, number 000042333, is the cited advisory, but its content did not load for me. Confirm any extra steps there.
The affected piece is the bgAutoinstaller service modules on Windows. The NVD record was published on 29 January 2024. The vector is local with low privileges, and the scope is changed, which means the effect reaches beyond the vulnerable component.
How to check if you're exposed
On a Windows endpoint, open Settings, Apps, Installed apps and read the version for the Forcepoint agent. Your endpoint management console should also report agent versions across the fleet.
Compare with 1.7.0.230330-554. Any lower build should be updated.
What to do now
- Report the agent version on every Windows endpoint through your management console.
- Update to 1.7.0.230330-554 or later using your normal software distribution.
- Check endpoints that rarely connect, such as laptops, since they may lag behind.
- Limit local administrator rights so a low privileged account cannot reach the service.
- Read the vendor article for related guidance.
Why it matters
CWE-862 is missing authorization. A privileged service accepts a request from a lower privileged user without checking whether that user is permitted to make it. The result is privilege escalation and a bypass of the functionality the agent enforces.
Security agents run with high privilege on every endpoint, which makes local flaws in them attractive. The record scores high integrity and availability impact. KEV is false and the record contains no evidence of exploitation. An agent that enforces policy should not be possible to bypass from a standard account.
When you update a security agent, test the new version on a small group first, then roll it out in waves. Agents that run at high privilege can cause outages if an update misbehaves, and a staged rollout lets you catch that early. Record the build number that each endpoint reports before and after the update, so you can show later that the fix reached every device.
Quick check
Which version fixes CVE-2023-1705?
1.7.0.230330-554. Versions before it are affected.
Does it need network access?
No. The vector is local and needs a low privileged account.
Sources
You can also run the free in-browser dependency scan at gold.safeguard.sh/scan to see which known vulnerabilities your dependencies carry.
Last reviewed: 19 October 2026.