CVE-2019-12289
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 · uneditedAn issue was discovered in upgrade_firmware.cgi on VStarcam 100T (C7824WIP) CH-sys-48.53.75.119~123 and 200V (C38S) CH-sys-48.53.203.119~123 devices. A remote command can be executed through a system firmware update without authentication. The attacker can modify the files within the internal firmware or even steal account information by executing a command.
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 confidenceUnauthenticated command injection vulnerability in the upgrade_firmware.cgi script on VStarcam C7824WIP and C38S IP cameras allows remote attackers to execute arbitrary system commands via the firmware update mechanism without any authentication. Attackers can modify firmware files or steal account credentials.
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= ch-sys-48.53.75.119\~123= ch-sys-48.53.203.119\~123CVSS 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 VStarcam IP cameras on the networkScan your network for devices with VStarcam vendor OUI or look for C7824WIP or C38S model designations in your device inventory or DHCP leasesAffected if Devices are VStarcam C7824WIP or C38S IP cameras
-
Check the installed firmware versionAccess the camera web interface and navigate to the settings or system information page to view the firmware version, or query the device via SNMP or manufacturer-specific API if availableAffected if Firmware version is ch-sys-48.53.75.119 through ch-sys-48.53.75.123 for C7824WIP, or ch-sys-48.53.203.119 through ch-sys-48.53.203.123 for C38S
-
Verify the web interface is accessibleAttempt to access the camera's HTTP/HTTPS web interface from the network where the camera is deployedAffected if The camera web interface responds and upgrade_firmware.cgi is present
-
Confirm firmware update functionality is enabledCheck if the firmware upgrade feature is accessible without authentication in the camera web interface, typically under Settings > System > Firmware Upgrade or similar pathAffected if The upgrade_firmware.cgi script is accessible without requiring login credentials
A user is affected if they have VStarcam C7824WIP or C38S cameras with firmware versions in the ch-sys-48.53.75.119-123 or ch-sys-48.53.203.119-123 ranges, and the web interface with upgrade_firmware.cgi is accessible on the network.
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 dataIsolate affected devices on restricted network segments; monitor for unauthorized firmware update attempts; contact vendor for firmware patch; if no patch available, replace vulnerable devices.
- Consultation2.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12289 — 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-12289 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