Kylin System UpdaterApplication · Kylinos

CVE-2023-7093

HIGH · 7.8 CVSS v3.1 Published 2023-12-25
Fix available
A fix is available. Upgrade to after 2.0.5.16-0k2.33 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability classified as critical has been found in KylinSoft kylin-system-updater up to 2.0.5.16-0k2.33. Affected is an unknown function of the file /usr/share/kylin-system-updater/SystemUpdater/UpgradeStrategiesDbus.py of the component com.kylin.systemupgrade Service. The manipulation of the argument SetDownloadspeedMax leads to os command injection. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-248940. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A local command injection vulnerability exists in KylinSoft kylin-system-updater (versions up to 2.0.5.16-0k2.33) in the UpgradeStrategiesDbus.py file via the com.kylin.systemupgrade dbus service. The SetDownloadspeedMax argument is not properly sanitized before being used in OS command execution, allowing a local attacker to execute arbitrary commands.

MitigationRestrict access to the com.kylin.systemupgrade dbus service, disable or remove the vulnerable kylin-system-updater component, or implement input validation on the SetDownloadspeedMax parameter to prevent command injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Kylin System UpdaterApplication
Affected:<= 2.0.5.16-0k2.33

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify kylin-system-updater installation and version
    Run 'rpm -qa | grep kylin-system-updater' or 'dpkg -l | grep kylin-system-updater' to list the installed package and its version
    Affected if The installed version is 2.0.5.16-0k2.33 or lower, or if the package name appears in the output at all
  2. Confirm dbus service availability
    Run 'dbus-send --system --print-reply --dest=com.kylin.systemupgrade /com/kylin/systemupgrade org.freedesktop.DBus.Introspectable.Introspect' to test if the com.kylin.systemupgrade dbus service is accessible
    Affected if The dbus service responds or is reachable, indicating the vulnerable interface is exposed
  3. Locate the vulnerable UpgradeStrategiesDbus.py file
    Search for the file using 'find / -name UpgradeStrategiesDbus.py 2>/dev/null' or check common paths like '/usr/lib/kylin-system-updater/' or '/opt/kylin-system-updater/'
    Affected if The file exists on the system, confirming the vulnerable component is present
  4. Check if the SetDownloadspeedMax method is exposed
    Use 'gdbus call --system --dest com.kylin.systemupgrade --object-path /com/kylin/systemupgrade --method com.kylin.systemupgrade.SetDownloadspeedMax test' to verify the method exists
    Affected if The method call succeeds or returns a response, confirming the exploitable function is available

If kylin-system-updater is installed at version 2.0.5.16-0k2.33 or lower AND the com.kylin.systemupgrade dbus service is accessible with the SetDownloadspeedMax method available, the environment is affected by CVE-2023-7093.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2.0.5.16-0k2.33
Interim mitigation

Restrict access to the com.kylin.systemupgrade dbus service, disable or remove the vulnerable kylin-system-updater component, or implement input validation on the SetDownloadspeedMax parameter to prevent command injection.

Fix this in Kylin System Updater Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-7093 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-7093 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data