CVE-2021-35233
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 · uneditedThe HTTP TRACK & TRACE methods were enabled in Kiwi Syslog Server 9.7.1 and earlier. These methods are intended for diagnostic purposes only. If enabled, the web server will respond to requests that use these methods by returning exact HTTP request that was received in the response to the client. This may lead to the disclosure of sensitive information such as internal authentication headers appended by reverse proxies.
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 confidenceThe HTTP TRACK and TRACE methods are enabled in Kiwi Syslog Server 9.7.1 and earlier. These diagnostic methods echo back the exact HTTP request received, including all headers, which can expose sensitive authentication headers (like Authorization or X-Forwarded-* headers) that reverse proxies may append to requests.
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<= 9.7.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Kiwi Syslog Server is installedCheck for the presence of Kiwi Syslog Server in Program Files or look for the service named 'Kiwi SyslogServer' in Windows ServicesAffected if Kiwi Syslog Server is installed on the system
-
Determine the installed Kiwi Syslog Server versionOpen the Kiwi Syslog Server GUI, go to Help > About, or check the version in Add/Remove Programs. Compare the version number to 9.7.2Affected if The installed version is 9.7.2 or earlier
-
Locate the Kiwi Syslog web interface configurationFind the web.config file in the Kiwi Syslog web application's directory, typically in the web subfolder of the installation pathAffected if A web.config file exists for Kiwi Syslog web interface
-
Check if HTTP TRACK method is enabledInspect the web.config file or IIS request filtering settings for the presence of the TRACK verb in allowedMethods. Alternatively, send a request with method TRACK to the Kiwi Syslog web interface and observe if a response is returnedAffected if The TRACK method is explicitly allowed or not blocked in the configuration
-
Check if HTTP TRACE method is enabledInspect the web.config file or IIS request filtering settings for the presence of the TRACE verb in allowedMethods. Alternatively, send a request with method TRACE to the Kiwi Syslog web interface and observe if a response is returnedAffected if The TRACE method is explicitly allowed or not blocked in the configuration
A system is affected if Kiwi Syslog Server version 9.7.2 or earlier is installed AND the HTTP TRACK or TRACE methods are enabled in the web server configuration, allowing potential header exposure.
Generated from the published advisory. Verify against your own configuration.
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 · scopedDisable the HTTP TRACK and TRACE methods in the web server (IIS) configuration or web.config file, or upgrade to a version where these methods are disabled by default.
- Access the Kiwi Syslog Server web interface configuration
- Locate the web server settings or HTTP server configuration
- Disable or remove the HTTP TRACK and TRACE methods from the allowed methods list
- Save the configuration changes
- Restart the Kiwi Syslog Server service to apply changes
- Verify that the server no longer responds to TRACE and TRACK HTTP methods by sending test requests
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2021-35233 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-35233 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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