CVE-2015-0929
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 · uneditedtime.htm in the web interface on SerVision HVG Video Gateway devices with firmware before 2.2.26a78 allows remote attackers to bypass authentication and obtain administrative access by leveraging a cookie received in an HTTP response.
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 confidenceThe time.htm page in the web interface of SerVision HVG Video Gateway devices with firmware before 2.2.26a78 contains an authentication bypass vulnerability. Attackers can obtain administrative access by leveraging a cookie received in an HTTP response, effectively bypassing the authentication mechanism entirely.
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<= 2.2.26a77CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Confirm device model is SerVision HVG Video GatewayAccess the device web interface or check the device label/documentation to verify the model is SerVision HVG Video GatewayAffected if Device is not a SerVision HVG Video Gateway
-
Check the installed firmware versionLog into the web interface and navigate to the firmware/version information page, or check via administrative console. Compare the version number to the affected range.Affected if Firmware version is 2.2.26a77 or earlier (less than 2.2.26a78)
-
Verify web interface is accessible on the networkAttempt to access the device web interface via HTTP/HTTPS from a browser or curl commandAffected if Web interface is reachable and responds to requests
-
Test time.htm for authentication bypassSend an HTTP GET request to the /time.htm endpoint without providing any authentication credentials or cookiesAffected if The time.htm page loads successfully without requiring authentication
The device is affected if it is a SerVision HVG Video Gateway running firmware version 2.2.26a77 or earlier and the time.htm page is accessible without authentication.
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 · scopedUpgrade the SerVision HVG Video Gateway firmware to version 2.2.26a78 or later to remediate the authentication bypass in the web interface.
Firmware version 2.2.26a78 or later
- 1. Access the SerVision HVG Video Gateway web interface and navigate to the admin/settings section to verify the current firmware version.
- 2. If the firmware version is 2.2.26a77 or earlier, navigate to the firmware update or system maintenance section.
- 3. Download the updated firmware version 2.2.26a78 or later from the SerVision support website or authorized distribution channel.
- 4. Follow the vendor's documented firmware upgrade procedure to apply the update, which typically involves uploading the firmware file through the web interface.
- 5. After the upgrade completes, verify that the firmware version now shows 2.2.26a78 or later.
- 6. Test that the time.htm page now requires proper authentication and cannot be accessed without valid credentials.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0929 — 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-2015-0929 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