Kofax Capture, now referred to as Tungsten Capture, version 6.0.0.0 (other versions may be affected) exposes a deprecated .NET Remoting HTTP channel on port 2424 via the Ascent Capture Service that is accessible without authentication and uses a default, publicly known endpoint identifier. An unauthenticated remote attacker can exploit .NET Remoting object unmarshalling techniques to instantiate a remote System.Net.WebClient object and read arbitrary files from the server filesystem, write attacker-controlled files to the server, or coerce NTLMv2 authentication to an attacker-controlled host, enabling sensitive credential disclosure, denial of service, remote code execution, or lateral movement depending on service account privileges and network environment.
Security readout for executives and security teams
Plain-English summary
An internet or network attacker may access vulnerable Capture servers without credentials, steal or alter files, or force credential authentication toward attacker infrastructure. Consequences depend on the service account and network controls, but could include business disruption, credential exposure, system compromise, and lateral movement.
Executive priority
Treat confirmed 6.0.0.0 deployments as an immediate remediation priority, especially when port 2424 is broadly reachable. Rapidly reduce network exposure and service privileges while obtaining authoritative vendor remediation guidance. Investigate possible credential exposure where suspicious outbound SMB activity exists.
Technical view
Kofax Capture 6.0.0.0 exposes an unauthenticated .NET Remoting HTTP channel through the Ascent Capture Service on TCP port 2424. The known default endpoint permits unsafe remote object unmarshalling, enabling arbitrary server-side file reads and writes or outbound NTLMv2 authentication coercion. The CVSS 3.1 score is 9.8.
Likely exposure
Systems running Kofax Capture 6.0.0.0 with the Ascent Capture Service reachable on TCP 2424 are most likely exposed. Other versions may be affected, but evidence is incomplete. Risk increases where the service account accesses sensitive files or outbound SMB and NTLM traffic is permitted.
Exploitation context
Public technical details exist, increasing practical attacker awareness. The supplied sources do not establish active exploitation, and this CVE is not identified as CISA KEV-listed. No authentication or user interaction is required according to the CVSS vector.
Researcher notes
The evidence identifies missing authentication and server-side request coercion weaknesses, mapped to CWE-306 and CWE-441. Confirmed impact applies to version 6.0.0.0; broader version coverage remains uncertain. The supplied material names no vendor patch, fixed release, or configuration workaround, so those details require vendor confirmation.
Mitigation direction
Restrict TCP port 2424 to explicitly trusted management systems and networks.
Block unnecessary outbound SMB and NTLM authentication from Capture servers.
Run the Ascent Capture Service with the minimum required filesystem and network privileges.
Check Tungsten Automation guidance for supported versions, patches, upgrades, or service configuration changes.
Monitor affected servers for unexpected file changes and outbound authentication attempts.
Validation and detection
Inventory Kofax or Tungsten Capture installations and confirm exact deployed versions.
Determine whether the Ascent Capture Service is enabled and listening on TCP port 2424.
Verify that untrusted networks cannot reach the service endpoint.
Review service-account permissions to files, network shares, and administrative resources.
Inspect logs for unusual port 2424 access, file activity, or outbound SMB authentication.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
CWE-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.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
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.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
2CVSS vectors
4Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-306 · source CWE mapping
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.
Unintended Proxy or Intermediary ('Confused Deputy')
Unintended Proxy or Intermediary ('Confused Deputy') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.