CVE-2023-40708
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 File Transfer Protocol (FTP) port is open by default in the SNAP PAC S1 Firmware version R10.3b. This could allow an adversary to access some device files.
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 SNAP PAC S1 industrial controller runs an FTP server by default on firmware R10.3b, exposing the device's file system over the network without encryption. An unauthenticated attacker on the network could connect to the open FTP port and read or write device files, potentially extracting sensitive configuration data or modifying device operation.
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= r10.3bCVSS 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 the device modelAccess the device's web interface or use network discovery to confirm the device is an Opto22 Snap Pac S1 controller. Check the device name or model number in the administration interface.Affected if The device is not a Snap Pac S1 controller, then it is not affected by this specific CVE.
-
Check the firmware versionIn the Snap Pac S1 web interface, navigate to Hardware > Controller Info or System > About to view the installed firmware version. Compare it to r10.3b.Affected if The firmware version is exactly r10.3b. Versions before or after this release may have different default configurations.
-
Verify FTP service statusAccess the device configuration through the web interface and check under Network Services or FTP Settings to see if the FTP server is enabled.Affected if The FTP service is enabled and running on the device. If FTP is disabled, the vulnerability does not apply.
-
Check FTP port accessibilityUse a network port scanner (such as nmap) from an external host to scan the device IP for open port 21 (FTP). Command: nmap -p 21 <device_ip>Affected if Port 21 is open and accepting connections from the network. This indicates FTP is network-accessible.
-
Confirm FTP authentication requirementAttempt an anonymous FTP connection to the device IP using an FTP client: ftp <device_ip>. Observe if access is granted without credentials.Affected if FTP accepts connections without authentication (anonymous access allowed), allowing unauthenticated file system access.
The environment is affected if it is a Snap Pac S1 controller running firmware r10.3b with the FTP service enabled and accessible over the network without authentication.
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 dataDisable the FTP service on the device if not required for operations. If FTP is necessary, implement network segmentation to restrict access to trusted hosts only, and consider migrating to secure file transfer protocols.
- 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-2023-40708 — 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-40708 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