CVE-2013-3689
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 · uneditedBrickcom FB-100Ap, WCB-100Ap, MD-100Ap, WFB-100Ap, OB-100Ae, OSD-040E, and possibly other camera models with firmware 3.0.6.16C1 and earlier, do not properly restrict access to configfile.dump, which allow remote attackers to obtain sensitive information (user names, passwords, and configurations) via a get action.
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 Brickcom IP camera models (FB-100Ap, WCB-100Ap, MD-100Ap, WFB-100Ap, OB-100Ae, OSD-040E) with firmware 3.0.6.16C1 and earlier contain an information disclosure vulnerability. The web interface does not properly restrict access to the configfile.dump file, allowing unauthenticated remote attackers to retrieve sensitive configuration data including user credentials and system settings via a simple HTTP GET request.
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<= 3.0.6.16c1all 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 Brickcom camera modelAccess the camera web interface or check device labels/documentation to confirm the exact model: FB-100Ap, WCB-100Ap, MD-100Ap, WFB-100Ap, OB-100Ae, or OSD-040EAffected if The device is one of these six Brickcom models
-
Check firmware versionLog into the camera web interface and navigate to System Settings or Status page to view the firmware version, or query the device via SNMP or the manufacturer's management toolAffected if Firmware version is 3.0.6.16C1 or earlier, or for FB-100Ap/MD-100Ap/OB-100Ae/OSD-040E/WCB-100Ap/WFB-100Ap any version since some are listed as all versions affected
-
Test configfile.dump accessibilitySend an HTTP GET request to http://<camera_ip_address>/configfile.dump using a web browser or curl command without providing any login credentialsAffected if The file downloads or displays configuration contents without requiring authentication
-
Verify sensitive data exposureOpen the downloaded configfile.dump and search for user account entries, passwords, admin credentials, or system configuration parametersAffected if Usernames, passwords, or other sensitive system settings are visible in plain text within the file
If the camera is an affected Brickcom model and the configfile.dump file is retrievable without authentication, the environment is vulnerable to CVE-2013-3689
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 version newer than 3.0.6.16C1. If no updated firmware is available, restrict network access to the camera management interface using firewall rules or VLAN segmentation, and immediately change any exposed credentials.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3689 — 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-3689 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