CVE-2018-7780
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 · uneditedIn Schneider Electric Pelco Sarix Professional 1st generation cameras with firmware versions prior to 3.29.69, a buffer overflow vulnerability exist in cgi program "set".
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 confidenceA buffer overflow vulnerability exists in the CGI program 'set' on Schneider Electric Pelco Sarix Professional 1st generation cameras running firmware versions prior to 3.29.69. This allows remote attackers to execute arbitrary code via crafted HTTP requests to the affected CGI endpoint.
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< 3.29.69< 3.29.69< 3.29.69< 3.29.69< 3.29.69< 3.29.69< 3.29.69< 3.29.69CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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 the camera modelAccess the camera's web interface or check the device label/metadata to confirm the exact model number (e.g., Imps110 1, Imp1110 1e, Ibps110 1er, etc.)Affected if The model is any of: Imps110 1, Imps110 1e, Imps110 1er, Ibps110 1er, Imp1110 1, Imp1110 1e, Imp1110 1er, Ibp1110 1er
-
Check the installed firmware versionLog into the camera's web interface and navigate to the About or System Information page to view the firmware version, or query the camera's API if availableAffected if The firmware version is lower than 3.29.69
-
Verify the set CGI endpoint is accessibleAttempt to access the /set CGI endpoint on the camera (e.g., http://<camera_ip>/set) using a web browser or HTTP clientAffected if The endpoint returns a valid response rather than a 404 error, indicating the CGI program is present
-
Assess network exposure of the management interfaceDetermine if the camera's web management interface (port 80/443) is reachable from untrusted networks or the internet by reviewing firewall rules and network segmentationAffected if The camera management interface is exposed to untrusted networks without firewall restrictions
The environment is affected if the camera model matches one of the listed products AND the firmware version is below 3.29.69 AND the set CGI endpoint is accessible.
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 · scoped3.29.69
Update camera firmware to version 3.29.69 or later. If immediate updating is not feasible, implement network segmentation and restrict access to the camera management interface to reduce exposure.
Firmware version 3.29.69 or later for Pelco Sarix Professional 1st generation cameras (Imps110, Imps110 1e, Imps110 1er, Ibps110 1er, Imp1110, Imp1110 1e, Imp1110 1er, Ibp1110 1er)
- Download firmware version 3.29.69 or later from Schneider Electric's official support website (www.schneider-electric.com)
- Access the Pelco Sarix camera web interface using an administrator account
- Navigate to the System or Maintenance section of the web interface
- Locate the Firmware Upgrade or Software Update option
- Upload the downloaded firmware file (.bin or .pkg)
- Wait for the upgrade process to complete - do not power off the camera during the update
- After reboot, verify the firmware version has been updated to 3.29.69 or later in the camera's status page
- Confirm the 'set' CGI program vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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 $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7780 — 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-2018-7780 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