dbcve.org
Kiwi Syslog ServerApplication · Solarwinds

CVE-2021-35236

MEDIUM · 5.3 CVSS v3.1 Published 2021-10-27
Fix available
A fix is available. Upgrade to after 9.7.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
The Secure flag is not set in the SSL Cookie of Kiwi Syslog Server 9.7.2 and previous versions. The Secure attribute tells the browser to only send the cookie if the request is being sent over a secure channel such as HTTPS. This will help protect the cookie from being passed over unencrypted requests. If the application can be accessed over both HTTP, there is a potential for the cookie can be sent in clear text.

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 versions 9.7.2 and prior fail to set the Secure flag on SSL cookies. Without this attribute, browsers will transmit session cookies over unencrypted HTTP connections, potentially exposing them to eavesdropping or man-in-the-middle attacks if the application is accessible over both HTTP and HTTPS.

MitigationConfigure the application or web server to set the Secure attribute on all cookies, ensuring they are only transmitted over encrypted HTTPS connections.

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.7.2

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

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. Identify installed Kiwi Syslog Server version
    Check the program's About or version information within the Kiwi Syslog Server interface, or locate the installed version through Windows Programs and Features
    Affected if The installed version is 9.7.2 or any prior version (9.x.y where y <= 2)
  2. Confirm web interface accessibility over HTTP
    Attempt to access the Kiwi Syslog Server web interface using http:// (not https://) on the configured port (default 8088 or 8080)
    Affected if The web interface responds over unencrypted HTTP connections
  3. Inspect cookie headers for Secure attribute
    Use browser developer tools or a network capture tool (like Wireshark or Fiddler) to capture the HTTP response headers when logging into the Kiwi Syslog Server web interface. Look for Set-Cookie headers and check if the Secure flag is present
    Affected if Session cookies are set without the Secure attribute (the cookie definition does not include the Secure flag)
  4. Verify mixed HTTP/HTTPS accessibility
    Determine if the Kiwi Syslog Server web server is configured to accept both HTTP and HTTPS connections, or if it can be accessed via either protocol
    Affected if The application is accessible over both HTTP and HTTPS, or can be forced to use HTTP

You are affected if Kiwi Syslog Server version 9.7.2 or earlier is installed AND the web interface is accessible over HTTP, with session cookies lacking the Secure flag in their Set-Cookie headers.

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 a release after 9.7.2
Interim mitigation

Configure the application or web server to set the Secure attribute on all cookies, ensuring they are only transmitted over encrypted HTTPS connections.

Recommended fix Moderate confidence

Kiwi Syslog Server 9.7.3 or later (verify against SolarWinds release notes)

  1. 1. Check the SolarWinds Kiwi Syslog Server release notes or security advisories for version 9.7.3 or later to confirm the Secure cookie flag vulnerability (CVE-2021-35236) is addressed
  2. 2. Before upgrading, backup the Kiwi Syslog Server configuration and database
  3. 3. Download the latest stable version of Kiwi Syslog Server from the official SolarWinds download page
  4. 4. Install the upgrade following the standard SolarWinds upgrade procedure
  5. 5. After upgrade, verify that the Set-Cookie headers for session cookies include the Secure attribute by inspecting HTTP responses in a browser dev tool or using a packet capture tool
Caveat Review upgrade notes for any configuration changes or migration requirements between 9.7.x versions

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

Fix this in Kiwi Syslog Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-35236 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