PXLSecurity LTD., Sofia, Bulgaria Offensive security since 2014[email protected]

CVE-2023-0830

EasyNAS OS command injection

Authenticated OS command injection in the system function of /backup.pl, reachable over the network.

OS command injectionEasyNASHigh

Technical summary

EasyNAS is a web-managed storage appliance. Its /backup.pl CGI script passes attacker-influenced data into Perl’s system function, so that data is interpreted by the shell rather than treated as an operand.

The published vectors put the attack vector at network and privileges required at low; VulDB’s own submission titles the issue “Authenticated OS Command Injection”, so an account on the appliance is needed. Four published scores exist and they disagree sharply on impact — NVD rates it 8.8 High, VulDB 6.3 Medium under CVSS 3.1 and 5.3 Medium under CVSS 4.0. All are shown above as published.

Impact

Command execution on the appliance in the context of the web application, which on a storage appliance means access to the data it serves.

A vulnerability classified as critical has been found in EasyNAS 1.1.0. Affected is the function system of the file /backup.pl. The manipulation leads to os command injection.

Remediation

The published record names no fixed version and no vendor advisory, so neither is stated here.

Published severity

Published byVersionBase scoreVector
NVDCVSS 3.1 8.8 High CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
VulDB (CNA)CVSS 4.0 5.3 Medium CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
VulDB (CNA)CVSS 3.1 6.3 Medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
VulDB (CNA)CVSS 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P

More than one organisation has scored this issue. We reproduce every published score and vector as published, attributed to its source, and do not compute our own.

Disclosure timeline

  1. 2023-02-14Advisory disclosed
  2. 2023-02-14CVE record published

Dates as recorded in the CVE record’s own timeline field. See the record.

References

Credit

Researcher: Ivan Spiridonov

Credited in the CVE record, under Ivan Spiridonov’s published handle, as reporter and analyst.

This is the work we do commercially

Vulnerability research and penetration testing by the same engineers who found this issue. Every report carries reproduction steps, impact and a retest.

We publish advisories, not exploits. Each entry describes the vulnerability class and impact at the level the vendor advisory does, and links to the authoritative records. Where public proof-of-concept code exists we link to it rather than reproduce it.

How we disclose

Every issue here was reported to the vendor or to a coordinating programme before publication. We publish only once a fix is available or the coordinated disclosure window has elapsed.

Want this kind of scrutiny on your own software?

Tell us what you want to protect. A senior tester will help you agree the scope and next steps. We usually reply within one business day.

Confidential from the first conversation

We can sign your NDA before you share sensitive details. Your enquiry is covered by our privacy policy.

How we protect your information · Privacy policy