CVE-2026-32964
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 · uneditedSD-330AC and AMC Manager provided by silex technology, Inc. contain an improper neutralization of CRLF sequences ('CRLF Injection') vulnerability. Processing some crafted configuration data may lead to arbitrary entries injected to the system configuration.
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 · moderate confidenceThe SD-330AC device and AMC Manager software contain a CRLF Injection vulnerability in their configuration data processing. Attackers can inject Carriage Return Line Feed (CRLF) sequences into configuration data, allowing arbitrary entries to be added to the system configuration. This improper neutralization of special characters enables manipulation of configuration parsing.
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< 1.50< 5.1.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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 SD-330AC firmware versionAccess the device web interface or administrative console and locate the firmware version information, typically found under System Info, Status, or Device Settings.Affected if The displayed firmware version is lower than 1.50
-
Identify AMC Manager software versionOpen AMC Manager and navigate to Help > About, or check the installed programs list in the operating system to locate the software version.Affected if The installed AMC Manager version is lower than 5.1.0
-
Verify configuration data access is availableLocate the configuration data input interface on the device web console or within AMC Manager, typically under Configuration, Settings, or Network settings sections.Affected if Configuration data input fields are accessible and available for modification
-
Test for CRLF injection point in configuration inputsSubmit configuration data containing CRLF sequences (or URL-encoded %0D%0A) to any configuration input field and observe if the sequences are processed or stored without neutralization.Affected if CRLF sequences are accepted and persisted in the configuration without being rejected or sanitized
You are affected if you are running SD-330AC firmware below version 1.50 or AMC Manager below version 5.1.0 AND you have access to configuration data input features that accept and process user-supplied values.
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 · scoped1.505.1.0
Implement proper input validation and sanitization for all configuration data, specifically neutralizing or rejecting CRLF sequences (%0D%0A) during processing. Validate that configuration inputs conform to expected formats before acceptance.
SD-330AC Firmware >= 1.50 and AMC Manager >= 5.1.0
- 1. Identify the current firmware version of the SD-330AC device by accessing its administration interface or checking the device status page
- 2. Identify the current version of AMC Manager by opening the application and navigating to Help > About, or checking the installed programs list
- 3. For SD-330AC: Download the firmware version 1.50 or later from the official silex technology support website (www.silex.jp)
- 4. For AMC Manager: Download version 5.1.0 or later from the official silex technology support website (www.silex.jp)
- 5. Apply the firmware update to the SD-330AC device following the manufacturer's upgrade instructions (typically via web UI or dedicated upgrade tool)
- 6. Install AMC Manager version 5.1.0 or later on the management system
- 7. After upgrading, verify the new versions are correctly installed and the services are functioning normally
- 8. Test that configuration data processing works correctly with the updated versions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32964 — 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-2026-32964 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