CVE-2019-10956
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 · uneditedGeutebruck IP Cameras G-Code(EEC-2xxx), G-Cam(EBC-21xx/EFD-22xx/ETHC-22xx/EWPC-22xx): All versions 1.12.0.25 and prior may allow a remote authenticated user, using a specially crafted URL command, to execute commands as root.
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 command injection vulnerability in Geutebruck IP cameras allows remote authenticated users to execute arbitrary commands as root via specially crafted URL commands. The vulnerability affects G-Code EEC-2xxx and G-Cam EBC-21xx/EFD-22xx/ETHC-22xx/EWPC-22xx models running firmware version 1.12.0.25 and prior.
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.12.0.25<= 1.12.0.25<= 1.12.0.25<= 1.12.0.25<= 1.12.0.25<= 1.12.0.25<= 1.12.0.25<= 1.12.0.25CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 web interface and check the system information or firmware version page, or use the ONVIF probe or manufacturer discovery tool to enumerate device details.Affected if The model is a Geutebruck G-Code EEC-2xxx, G-Cam EBC-21xx, EFD-22xx, ETHC-22xx, or EWPC-22xx device.
-
Check the firmware versionIn the camera web interface, navigate to the System, Info, or About section to view the installed firmware version.Affected if The firmware version is 1.12.0.25 or earlier.
-
Verify web interface accessibilityAttempt to access the camera HTTP/HTTPS management port from a network location or use a port scanner to confirm if TCP ports 80, 443, or 8080 are listening and reachable.Affected if The camera web management interface is exposed on the network.
-
Review authentication configurationCheck if default administrative credentials are still in use or if strong password policies are enforced on the camera user accounts.Affected if Default credentials are unchanged or weak passwords are configured, allowing authenticated access.
The environment is affected if the camera model matches one of the affected Geutebruck models, runs firmware version 1.12.0.25 or earlier, has its web interface network-accessible, and uses default or weak authentication credentials.
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 dataUpdate Geutebruck IP camera firmware to a version newer than 1.12.0.25. If no updated firmware is available, restrict network access to camera management interfaces to trusted users only and enforce strong authentication credentials.
- 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-2019-10956 — 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-2019-10956 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