Skip to main content

ipTIME NAS1dual EUVDEUVD-2026-27333

| CVE-2026-7834 HIGH
Stack-based Buffer Overflow (CWE-121)
2026-05-05 VulDB GHSA-c384-mhv7-jvfr
8.9
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Identify exposed NAS web interface
  2. Delivery
    Send crafted HTTP POST to /cgi/advanced/misc_main.cgi
  3. Exploit
    Overflow stack buffer in get_csrf_whites
  4. Install
    Overwrite return address with shellcode pointer
  5. C2
    Execute arbitrary code as root
  6. Execute
    Install persistent backdoor
  7. Impact
    Exfiltrate sensitive data

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

No special conditions - remote unauthenticated exploitation against default configurations of ipTIME NAS1dual. The CVSS vector confirms attack requirements: network accessibility (AV:N) to the web management interface, no authentication (PR:N), no user interaction (UI:N), and low attack complexity (AC:L). Exploitation requires only that the device's CGI interface at /cgi/advanced/misc_main.cgi be reachable over TCP/IP, which is typical for default NAS configurations where web management is enabled. The vulnerable get_csrf_whites function appears to be accessible without authentication, suggesting it may be part of pre-authentication CSRF protection logic ironically containing the vulnerability. No specific non-default features, services, or configuration changes are mentioned as prerequisites in the available data. Attack surface exists on any internet-facing deployment or from internal network positions if the device is deployed on corporate LANs. The attack is limited to ipTIME NAS1dual version 1.5.24 and potentially related versions indicated by the CPE wildcard; other ipTIME models or firmware versions are not confirmed affected based on available data.

Impact

This represents an elevated real-world risk despite limited data signals. CVSS 8.9 accurately reflects the technical severity: network-accessible (AV:N), low attack complexity (AC:L), no authentication required (PR:N), no user interaction (UI:N), and complete system impact (VC/VI/VA:H). The CVSS 4.0 Exploit Maturity indicator shows E:P (Proof-of-concept), confirmed by the publicly available GitHub repository containing exploitation details. However, critical risk signals are missing: no CISA KEV listing suggests this is not yet observed in widespread active exploitation, and EPSS probability data is unavailable for comparative risk assessment. The vendor's non-responsiveness to disclosure is concerning, indicating likely absence of official patches. Real-world risk factors favoring exploitation: unauthenticated remote vector, public POC, embedded device unlikely to receive automatic updates. Risk factors limiting exploitation: appears to be an IoT/embedded device with potentially limited deployment compared to enterprise infrastructure, and successful exploitation may require knowledge of specific input formatting to trigger the overflow. Priority assessment: High for organizations using ipTIME NAS devices; Medium-Low for general enterprise environments unless this specific hardware is deployed. The combination of remote unauthenticated access and public exploit code mandates immediate attention from affected users, but absence from CISA KEV suggests targeted rather than mass exploitation patterns currently.

Exploit ScenarioDerived

An external attacker identifies an ipTIME NAS1dual device exposed to the Internet through port scanning or IoT search engines like Shodan. The attacker sends a specially crafted HTTP request to /cgi/advanced/misc_main.cgi targeting the get_csrf_whites function with oversized input parameters that exceed the stack buffer allocation. The overflow overwrites the function's return address with attacker-controlled values, redirecting execution to injected shellcode. The attacker gains root-level code execution on the embedded Linux system, enabling data exfiltration of stored files, installation of persistent backdoors, or pivoting to other devices on the victim's internal network. Public proof-of-concept code on GitHub (https://github.com/glkfc/IoT-Vulnerability/blob/main/iptime/nas1dual/iptime2_en.md) provides technical details for exploitation, lowering the skill barrier for attack.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 05, 2026

Stack-based buffer overflow in EFM ipTIME NAS1dual 1.5.24 allows remote unauthenticated attackers to achieve complete system compromise via the get_csrf_whites function in /cgi/advanced/misc_main.cgi. Public exploit code exists on GitHub, demonstrating practical exploitability despite lack of vendor response to responsible disclosure. CVSS 8.9 (Critical) with EPSS data unavailable; attack requires no authentication, low complexity, and no user interaction (AV:N/AC:L/PR:N/UI:N), making this a high-priority remote attack surface.

RemediationAI

No vendor-released patch identified at time of analysis; EFM did not respond to vulnerability disclosure per the CVE description. Without official firmware updates, organizations must implement compensating controls immediately. Primary mitigation: Isolate ipTIME NAS1dual devices from Internet-facing networks by placing them behind firewall rules that restrict /cgi/advanced/ endpoints to trusted internal management networks only - this eliminates remote attack vector (AV:N) but reduces device accessibility for remote management. Secondary mitigation: If web interface access is required, implement reverse proxy authentication (such as nginx with HTTP basic auth) in front of the device to add the missing PR:N→PR:L authentication barrier, though this adds operational complexity and single point of failure. Tertiary option: Disable the web management interface entirely if device can be administered through alternative methods (SSH, serial console), though this may not be supported on consumer NAS models. Organizations should consider replacing affected devices with actively-supported alternatives given vendor non-responsiveness. Monitor network logs for HTTP requests to /cgi/advanced/misc_main.cgi with unusual Content-Length or payload characteristics. All mitigations trade functionality for security; network isolation is the most reliable control with least operational risk. Consult https://vuldb.com/vuln/361113/cti for additional vendor contact attempts and community-developed workarounds.

Affected VersionsENISA

ipTIME NAS1dual 1.5.24

Affected Packages

euvd iptime_nas1dual no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability exploits a classic stack-based buffer overflow (CWE-121) in the get_csrf_whites function within the CGI interface of ipTIME NAS1dual network-attached storage devices. Stack-based overflows occur when data exceeding allocated buffer size overwrites adjacent memory on the stack, potentially corrupting return addresses and enabling arbitrary code execution. The vulnerable endpoint (/cgi/advanced/misc_main.cgi) appears to be part of the device's web management interface, which is commonly exposed to network access. The CVSS vector indicates complete confidentiality, integrity, and availability impact to the vulnerable component (VC:H/VI:H/VA:H) with no cross-scope effects (SC:N/SI:N/SA:N), suggesting exploitation achieves full control of the NAS device itself. The CVE identifier appears to be from 2026, which may indicate a reporting/publication timing issue or test data.

Know when Iptime Nas1Dual gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 8.9 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

Primary rating from Vendor (VulDB) · only source for this CVE.

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Severity Changed
May 05, 2026 - 14:22 NVD
CRITICAL HIGH
CVSS changed
May 05, 2026 - 14:22 NVD
9.8 (CRITICAL) 8.9 (HIGH)

DescriptionCVE.org

A security vulnerability has been detected in EFM ipTIME NAS1dual 1.5.24. This issue affects the function get_csrf_whites of the file /cgi/advanced/misc_main.cgi. Such manipulation leads to stack-based buffer overflow. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Executive ViewAI

Why It Matters

CVE-2026-7834 is a critical stack-based buffer overflow affecting EFM ipTIME NAS1dual 1.5.24 that allows unauthenticated remote attackers to achieve complete system compromise through an exposed CGI endpoint. Organizations deploying this NAS appliance face immediate risk of data theft, ransomware deployment, and infrastructure takeover, as the vendor has not released a patch despite responsible disclosure efforts.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Block network access to /cgi/advanced/misc_main.cgi via firewall rules, (2) Disable CGI execution on the affected service if operationally feasible, (3) Deploy Web Application Firewall (WAF) rules to filter malformed requests to the vulnerable endpoint, (4) Implement network segmentation to restrict NAS access to authorized users only, (5) Enable enhanced monitoring and logging on the affected device for exploit attempt detection, (6) Maintain offline encrypted backups of critical NAS data independent of the appliance.

Threat Intelligence Overview

EPSS Score
0.0%
Top 88% exploitable
Exploit
POC
Public exploit code exists
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

64
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy