Kiwi Syslog ServerApplication · Solarwinds

CVE-2021-35231

MEDIUM · 6.7 CVSS v3.1 Published 2021-10-25
Fix available
A fix is available. Upgrade to 9.8 or later.
See remediation →
69/100
Remediation priority · Elevated
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
As a result of an unquoted service path vulnerability present in the Kiwi Syslog Server Installation Wizard, a local attacker could gain escalated privileges by inserting an executable into the path of the affected service or uninstall entry. Example vulnerable path: "Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Kiwi Syslog Server\Parameters\Application".

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

Kiwi Syslog Server contains an unquoted service path vulnerability where the service executable path contains spaces and is not enclosed in quotes. This allows Windows to search for executables in intermediate path components, enabling a local attacker to place a malicious executable (e.g., 'Program.exe') in a parent directory to achieve privilege escalation when the service restarts.

MitigationReinstall Kiwi Syslog Server to a path without spaces (e.g., C:\KiwiSyslog\), or manually correct the registry service path to include quotes around the executable path.

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
Kiwi Syslog ServerApplication
Affected:< 9.8

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 Kiwi Syslog Server service exists
    Open Services (services.msc) or run 'sc query' and look for a Kiwi Syslog related service entry
    Affected if No Kiwi Syslog Server service is found - the vulnerability does not apply
  2. Retrieve the service executable path
    Check the registry key HKLM\SYSTEM\CurrentControlSet\Services\<KiwiServiceName>\ImagePath, or run 'sc qc KiwiSyslogServer' to view the binary path
    Affected if The service exists but the ImagePath is not retrievable - further manual investigation needed
  3. Check if the path contains spaces
    Examine the ImagePath value - if it contains spaces between directory names (e.g., C:\Program Files\SolarWinds\...), this indicates the unquoted path condition
    Affected if The path contains spaces and is NOT enclosed in quotes - the environment is vulnerable
  4. Verify if path is properly quoted
    Confirm whether the entire executable path string begins and ends with double quotation marks
    Affected if The path contains spaces but lacks opening and closing quotes - the environment is vulnerable

A user is affected if the Kiwi Syslog Server service is installed and its executable path in the service configuration contains spaces without being enclosed in quotation marks.

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.

dbcve · scoped
Upgrade available Upgrade to 9.8 or later
Fixed in 9.8
Interim mitigation

Reinstall Kiwi Syslog Server to a path without spaces (e.g., C:\KiwiSyslog\), or manually correct the registry service path to include quotes around the executable path.

Recommended fix Moderate confidence

Kiwi Syslog Server 9.8 or later

  1. Back up current Kiwi Syslog Server configuration and data
  2. Download Kiwi Syslog Server version 9.8 or later from the official SolarWinds download portal
  3. Stop the Kiwi Syslog Server service before upgrading
  4. Install version 9.8 or newer using the updated Installation Wizard which fixes the unquoted service path vulnerability
  5. After installation, verify the service path is properly quoted in the Windows Registry at HKLM\SYSTEM\ControlSet001\Services\Kiwi Syslog Server\Parameters\Application
  6. Start the Kiwi Syslog Server service and verify normal operation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kiwi Syslog Server Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-35231 — 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-2021-35231 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