Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2023-54402 – Unauthenticated Arbitrary File Read / SSRF – iDocView < 13.10.1_20231115

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2023-54402 is a server-side request forgery (SSRF) vulnerability in iDocView, an online document preview application, affecting the /doc/upload endpoint. The endpoint relies on a hardcoded default authentication token, allowing remote, unauthenticated attackers to bypass access controls and force the server to fetch arbitrary URLs — including file:// URIs — leading to disclosure of local files and access to internal network resources. The flaw carries a CVSS v3.1 base score of 7.5 (CVSS v4.0: 8.7), both rated HIGH, and is listed as a known exploited vulnerability.

Technical details

  • Root cause: the /doc/upload endpoint accepts a token parameter that is validated against a hardcoded default value (testtoken), allowing any remote user who knows this value to bypass authentication.
  • Trigger condition: an attacker sends a request to /doc/upload with token=testtoken and a url parameter pointing to an arbitrary resource, including local files via the file:// scheme.
  • Attack vector: network-based, unauthenticated, no user interaction required.
  • Impact: the server fetches and returns the content of the attacker-supplied URL, enabling arbitrary local file read (e.g., OS and application configuration files) and server-side requests against internal network hosts and services that would otherwise be unreachable from outside the network.
  • Exploitation of this issue in the wild was first observed by the Shadowserver Foundation on 2024-03-26, and it is tracked as a known exploited vulnerability.

Affected software

  • iDocView — all versions (no version-specific fix has been identified; the vendor has not published version boundaries for the affected release range).

Severity

  • CVSS v3.1 Base Score: 7.5 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • CVSS v4.0 Base Score: 8.7 (HIGH) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: No vendor patch or fixed version has been publicly identified for this issue. Organizations running iDocView should contact the vendor for a fix or confirm whether a current release has removed the hardcoded default token.
  • If no patch is available: Restrict or remove public internet exposure of the /doc/upload endpoint; place it behind authentication enforced by a reverse proxy or WAF; block or filter requests containing file://, gopher://, or other non-HTTP URL schemes in the url parameter; monitor outbound requests from the application server for unexpected internal or local-file access; and isolate the host from sensitive internal network segments until remediated.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge