Security readout for executives and security teams
Plain-English summary
This is a local privilege escalation in Agnitum Outpost Internet Security 8.1. A user already on a Windows system could abuse the product’s privileged service to run code as SYSTEM. The main business risk is full takeover of legacy endpoints where this product remains installed.
Executive priority
Treat as high priority for legacy endpoint risk reduction. It is not a remote internet worm risk from the provided evidence, but it can turn a basic local foothold into complete system control.
Technical view
The reported flaw is in acs.exe, which exposes a named pipe accepting unauthenticated commands. The pipe protocol has a directory traversal weakness that can cause the service to load a DLL from a user-controlled location, executing it under the privileged service context.
Likely exposure
Exposure appears limited to Windows systems running Agnitum Outpost Internet Security 8.1. The attack requires local low-privileged access, so internet-facing exposure is not indicated by the provided sources.
Exploitation context
Public exploit references exist, including Metasploit and Exploit-DB entries. The bundle does not show CISA KEV listing or cited evidence of active exploitation in the wild.
Researcher notes
The key primitives are unauthenticated named-pipe command handling and directory traversal leading to privileged DLL loading. Evidence supports local privilege escalation, public exploit availability, and high impact, but not active exploitation or a named vendor patch.
Mitigation direction
- Inventory endpoints for Agnitum Outpost Internet Security 8.1.
- Check vendor or trusted advisory guidance for any supported remediation.
- Remove or replace affected installations where vendor guidance is unavailable.
- Restrict local user access on systems where the product remains installed.
- Monitor affected hosts for suspicious privileged service behavior.
Validation and detection
- Confirm whether acs.exe is present on Windows endpoints.
- Verify installed product name and version against Outpost Internet Security 8.1.
- Review local security telemetry for unexpected SYSTEM-level DLL loading.
- Prioritize validation on legacy or unmanaged endpoint groups.
- Avoid using public exploit modules on production systems.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2013-10046 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.5 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
8.5HighVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Source materials
- CVE List V5 sourceCVE List V5
- https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/windows/local/agnitum_outpost_acs.rbCVE reference · exploit
- https://www.exploit-db.com/exploits/27282CVE reference · exploit
- https://www.exploit-db.com/exploits/28335CVE reference · exploit
- https://www.vulncheck.com/advisories/agnitum-outpost-internet-security-local-priv-escCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.