CVE-2019-10958
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 attacker with access to network configuration to supply system commands to the server, leading to remote code execution 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 confidenceCommand injection vulnerability in Geutebruck IP cameras (G-Code EEC-2xxx and G-Cam EBC-21xx/EFD-22xx/ETHC-22xx/EWPC-22xx) versions 1.12.0.25 and prior. An authenticated attacker with network configuration access can inject arbitrary system commands, achieving remote code execution as the root user.
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's web interface or check the device label/datasheet to confirm the exact model (e.g., G-Code EEC-2400, G-Cam EBC-2110, EFD-2240, ETHC-2230, etc.)Affected if The model is one of the affected Geutebruck G-Code EEC-2xxx or G-Cam EBC-21xx/EFD-22xx/ETHC-22xx/EWPC-22xx series
-
Check the firmware versionLog into the camera web interface and navigate to System > Firmware or System > Information to view the installed firmware versionAffected if The firmware version is 1.12.0.25 or earlier
-
Verify network configuration access is enabledCheck the camera's web interface for the network configuration or administration settings module. This is typically found under Network > Configuration or Settings > NetworkAffected if The network configuration interface is accessible without additional access controls or is exposed to untrusted networks
-
Confirm authentication is requiredVerify that the camera requires valid credentials for accessing the web interface and network configuration functionsAffected if Anonymous or default credentials provide access, or authentication can be bypassed for the network configuration feature
The environment is affected if the camera is a Geutebruck G-Code or G-Cam model running firmware version 1.12.0.25 or lower, and the network configuration interface is accessible to an authenticated attacker.
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 dataUpgrade camera firmware to a patched version. If no patched firmware is available, restrict network access to the camera management interfaces to trusted users only, disable remote administration if not required, and monitor for indicators of compromise.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10958 — 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-10958 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