CVE-2013-3687
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 · uneditedAirLive POE2600HD, POE250HD, POE200HD, OD-325HD, OD-2025HD, OD-2060HD, POE100HD, and possibly other camera models use cleartext to store sensitive information, which allows attackers to obtain passwords, user names, and other sensitive information by reading an unspecified backup file.
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 confidenceMultiple AirLive IP camera models store sensitive credentials (usernames, passwords) in cleartext within backup files. An attacker with access to these unspecified backup files can retrieve the plaintext credentials and gain unauthorized access to the cameras and their streams.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:C/I:N/A:N
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 AirLive IP camera models on your networkScan your network inventory or physically inspect the devices to determine if any of the following models are present: Ovislink Airlive Od 2025hd, Od 2060hd, Poe100hd, Poe200hd, Poe250hd, or Poe2600hd. Check the device labels, web interface, or management console for the exact model number.Affected if Any of the listed AirLive camera models are present on your network, as all versions of these models store credentials in cleartext within backup files.
-
Locate backup files from AirLive camerasSearch for any backup, export, or configuration files that may have been created from these AirLive devices. Check the camera web interface for a backup/export feature, local storage locations, any network shares where backups may have been saved, and any system where you manage these devices.Affected if Backup files from these AirLive cameras exist in your environment, as the vulnerability lies within the backup file format itself.
-
Inspect backup file contents for cleartext credentialsOpen the backup file using a text editor or file extraction tool. Search within the file for plaintext strings that appear to be usernames and passwords. Look for patterns such as 'username=', 'password=', or any identifiable credential pairs stored in plain text rather than hashed or encrypted.Affected if The backup file contains readable (plaintext) usernames and passwords rather than encrypted or hashed credential representations.
-
Verify camera firmware version as secondary confirmationAccess the camera web interface and navigate to the system information or status page to confirm the firmware version. While all versions are affected, documenting the version helps confirm the device identity.Affected if The device firmware matches any version of the listed AirLive models, confirming the device falls within the affected product range.
You are affected if you have any Ovislink Airlive camera models Od 2025hd, Od 2060hd, Poe100hd, Poe200hd, Poe250hd, or Poe2600hd in your environment, and those devices have backup files that contain plaintext 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 dataRestrict access to backup files via proper file permissions and network segmentation; rotate all credentials immediately; contact vendor for firmware updates addressing encrypted credential storage; consider replacing affected devices if no patch is available.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3687 — 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-2013-3687 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