dbcve.org
One Smartedge AgentWeb browser · Forcepoint

CVE-2023-1705

HIGH · 7.8 CVSS v3.1 Published 2024-01-29
Fix available
A fix is available. Upgrade to 1.7.0.230330-554 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Missing Authorization vulnerability in Forcepoint F|One SmartEdge Agent on Windows (bgAutoinstaller service modules) allows Privilege Escalation, Functionality Bypass.This issue affects F|One SmartEdge Agent: before 1.7.0.230330-554.

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 · high confidence

A missing authorization vulnerability in the Forcepoint F|One SmartEdge Agent's bgAutoinstaller service modules on Windows allows local attackers to escalate privileges and bypass security functionality. The vulnerability stems from insufficient authorization checks in the agent's installation/update components, potentially enabling an unprivileged user to execute operations with elevated permissions.

MitigationUpgrade Forcepoint F|One SmartEdge Agent to version 1.7.0.230330-554 or later. As a compensating control, restrict access to the bgAutoinstaller service and monitor for suspicious installation activities.

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
One Smartedge AgentWeb browser
Affected:< 1.7.0.230330-554

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Forcepoint One SmartEdge Agent is installed
    Check for the presence of Forcepoint One SmartEdge Agent on the Windows system by looking for the product in Add/Remove Programs, or searching for Forcepoint installation directories (commonly in Program Files or Program Files (x86)).
    Affected if Forcepoint One SmartEdge Agent is found installed on the system.
  2. Identify installed version
    Locate the installed version information. Check the program's About dialog, version info in the installation directory, or use Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Forcepoint One SmartEdge Agent to find the Version string.
    Affected if The installed version is lower than 1.7.0.230330-554.
  3. Verify bgAutoinstaller service presence
    Open Services console (services.msc) or run 'sc query' command and search for a service named bgAutoinstaller or similar autoinstaller service related to Forcepoint.
    Affected if The bgAutoinstaller service exists and is running on the system.
  4. Check service configuration and permissions
    Run 'sc qc <servicename>' to query the service configuration, and check the binary path. Use 'icacls' on the service executable to examine what users have write or execute permissions.
    Affected if The service is configured to run with elevated privileges and unprivileged users have write access to the service binary or configuration.

A system is affected if Forcepoint One SmartEdge Agent is installed with a version lower than 1.7.0.230330-554 AND the bgAutoinstaller service is present and accessible to unprivileged users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.7.0.230330-554 or later
Fixed in 1.7.0.230330-554
Interim mitigation

Upgrade Forcepoint F|One SmartEdge Agent to version 1.7.0.230330-554 or later. As a compensating control, restrict access to the bgAutoinstaller service and monitor for suspicious installation activities.

Recommended fix Moderate confidence

1.7.0.230330-554

  1. 1. Identify the current version of Forcepoint F|One SmartEdge Agent installed on the Windows system
  2. 2. Navigate to the Forcepoint support portal (support.forcepoint.com) and locate the download for F|One SmartEdge Agent version 1.7.0.230330-554 or later
  3. 3. Download the updated agent installer package
  4. 4. Stop the bgAutoinstaller service and any related Forcepoint services before upgrading
  5. 5. Run the installer to upgrade the F|One SmartEdge Agent to version 1.7.0.230330-554 or latest available version
  6. 6. After installation completes, verify the new version is correctly installed
  7. 7. Restart the Forcepoint services and confirm the bgAutoinstaller service is running with proper authorization controls

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in One Smartedge Agent Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-1705 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-1705 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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