CyberSecBulletin
CVE-2023-47564NVD status: Modified

Qsync Central: Incorrect Permission Assignment for Critical Resource

Published Updated By the CyberSecBulletin desk

CVE-2023-47564 is a high-severity incorrect permission assignment for critical resource vulnerability in Qsync Central from QNAP, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 4.4.0.15 ( 2024/01/04 ), 4.3.0.11 ( 2024/01/11 ), 4.4.0.15 as the first without the flaw, so updating Qsync Central to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.01% chance of exploitation within 30 days, higher than 64% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Qsync Central to 4.4.0.15 ( 2024/01/04 ) or 4.3.0.11 ( 2024/01/11 ) or 4.4.0.15 or 4.3.0.11, whichever matches your release line, or a later version.
  2. Read the advisory on qnap.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
QNAPQsync Central4.4.x.x up to, but not including, 4.4.0.15 ( 2024/01/04 ); 4.3.x.x up to, but not including, 4.3.0.11 ( 2024/01/11 ); 4.4.0.0 up to, but not including, 4.4.0.15; 4.3.0.0 up to, but not including, 4.3.0.114.4.0.15 ( 2024/01/04 ), 4.3.0.11 ( 2024/01/11 ), 4.4.0.15, 4.3.0.11

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.0HighCNA (qnapsecurity.com.tw)
CVSS 3.18.1HighNVD

Official description

An incorrect permission assignment for critical resource vulnerability has been reported to affect Qsync Central. If exploited, the vulnerability could allow authenticated users to read or modify the resource via a network. We have already fixed the vulnerability in the following versions: Qsync Central 4.4.0.15 ( 2024/01/04 ) and later Qsync Central 4.3.0.11 ( 2024/01/11 ) and later

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Incorrect Permission Assignment for Critical Resource

The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

How developers prevent this class of flaw

  • When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
  • Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly. This will allow you to maintain more fine-grained control over your resources.
  • During program startup, explicitly set the default permissions or umask to the most restrictive setting possible. Also set the appropriate permissions during program installation. This will prevent you from inheriting insecure permissions from any user who installs or runs the program.

More Incorrect Permission Assignment for Critical Resource vulnerabilities (CWE-732)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Qsync Central

All Qsync Central vulnerabilities

Recent Incorrect Permission Assignment for Critical Resource vulnerabilities

Spotted an error? Tell us.