CVE-2023-35796
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 · uneditedA vulnerability has been identified in SINEMA Server V14 (All versions). The affected application improperly sanitizes certain SNMP configuration data retrieved from monitored devices. An attacker with access to a monitored device could perform a stored cross-site scripting (XSS) attack that may lead to arbitrary code execution with `SYSTEM` privileges on the application server. (ZDI-CAN-19823)
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 confidenceSINEMA Server V14 fails to sanitize SNMP configuration data received from monitored devices before storing/displaying it, creating a stored XSS vulnerability. An attacker with access to a monitored device can inject malicious JavaScript or script content via SNMP responses that executes in the context of the SINEMA Server application, ultimately achieving arbitrary code execution with SYSTEM privileges.
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= 14.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SINEMA Server installationLocate the SINEMA Server installation directory and check the application version information, typically found in the server's about or version info section of the web interface or in installed program filesAffected if The installed version is exactly 14.0
-
Verify SNMP monitoring feature is enabledAccess the SINEMA Server administrative interface and check the SNMP configuration or monitoring settings to determine if SNMP device monitoring is activeAffected if SNMP monitoring is enabled and the server is configured to receive SNMP data from monitored devices
-
Confirm monitored devices are configuredReview the device list or network monitoring configuration within SINEMA Server to see which devices are set up as monitored SNMP endpointsAffected if One or more monitored devices are configured to send SNMP traps or responses to the server
-
Inspect SNMP data storage locationsExamine the SINEMA Server database, log files, or web interface where SNMP configuration data from monitored devices is stored or displayed - look for unencoded HTML or script tags in SNMP-related fieldsAffected if SNMP data from monitored devices contains unsanitized JavaScript or script content that could execute in the browser
You are affected if SINEMA Server version 14.0 is running with SNMP monitoring enabled and configured to accept SNMP data from monitored devices.
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.
From vendor dataImplement strict input validation and output encoding for all SNMP data received from monitored devices; restrict which devices can send SNMP traps to the server via network segmentation; monitor for patches from Siemens.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35796 — 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-2023-35796 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