CVE-2018-7782
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, authenticated users can view passwords in clear text.
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 confidenceAuthenticated users on Schneider Electric Pelco Sarix Professional 1st generation cameras (firmware prior to 3.29.69) can view other users' passwords in clear text through the web interface or API. This is a cleartext password display vulnerability allowing confidentiality breach of credential data.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 camera modelAccess the camera web interface or check the device label/metadata to confirm the exact model (Imps110 1/1e/1er, Ibps110 1er, Imp1110 1/1e/1er, or Ibp1110 1er)Affected if Model matches one of the affected Pelco Sarix Professional 1st generation cameras
-
Check firmware versionIn the camera web interface, navigate to the About or System Information page and record the firmware version numberAffected if Firmware version is lower than 3.29.69 (for example, 3.28.x or earlier)
-
Verify web interface password exposureLog into the camera as an authenticated user, then navigate to the user management or administrator settings page where user accounts are listed; observe whether any password fields display actual password characters in clear text rather than masked dots or asterisksAffected if Clear text passwords are visible in the user management section of the web interface
-
Check API for cleartext passwordsIf API access is enabled, use an authenticated HTTP request to the user enumeration or configuration endpoint (such as /users or /config/user) and inspect the response payload for password fieldsAffected if API responses contain plaintext password values for user accounts
You are affected if your camera is a Pelco Sarix Professional 1st generation model (Imps110, Ibps110, Imp1110, or Ibp1110 variants) running firmware version 3.29.69 or lower AND an authenticated user can view other users passwords in clear text via the web interface or API.
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 data3.29.69
Update Pelco Sarix Professional 1st generation cameras to firmware version 3.29.69 or later. Restrict administrative access to the camera management interface until patching is complete.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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 $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7782 — 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-7782 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