CVE-2013-3690
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 · uneditedCross-site request forgery (CSRF) vulnerability in cgi-bin/users.cgi in Brickcom FB-100Ap, WCB-100Ap, MD-100Ap, WFB-100Ap, OB-100Ae, OSD-040E, and possibly other camera models with firmware 3.1.0.8 and earlier, allows remote attackers to hijack the authentication of administrators for requests that add users.
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 confidenceCross-site request forgery (CSRF) vulnerability in the cgi-bin/users.cgi script of Brickcom IP cameras (FB-100Ap, WCB-100Ap, MD-100Ap, WFB-100Ap, OB-100Ae, OSD-040E, and others) allows remote attackers to add administrative users by tricking authenticated administrators into visiting malicious pages, exploiting the lack of anti-CSRF tokens in the user management interface.
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.1.0.8all 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 device modelAccess the camera's web interface or check the device label/documentation to confirm it is a Brickcom model (FB-100Ap, WCB-100Ap, MD-100Ap, WFB-100Ap, OB-100Ae, OSD-040E, or 100ap series)Affected if The device is a Brickcom IP camera from the affected model list
-
Check the firmware versionLog into the camera's web interface and navigate to System > Firmware/Version, or use the cgi-bin/.../system.cgi endpoint to retrieve firmware information. Compare the installed version to 3.1.0.8Affected if Firmware version equals 3.1.0.8, or the model is FB-100Ap, MD-100Ap, OB-100Ae, OSD-040E, WCB-100Ap, or WFB-100Ap (all versions)
-
Verify the user management script existsAttempt to access the cgi-bin/users.cgi script on the camera (e.g., http://[camera-ip]/cgi-bin/users.cgi)Affected if The script is accessible and responds to requests
-
Check for anti-CSRF tokens in user management formsAccess the user management page (usually under Administration or Users in the web interface), view the page source or capture the HTTP GET request/response, and examine all form submissions for the presence of a unique token or nonce parameterAffected if No anti-CSRF token or unique parameter is present in user add/modify forms
-
Verify CSRF protection in HTTP responsesCapture HTTP responses from the camera's user management interface and check for CSRF-related headers (such as CSRF-Token or X-CSRF-Token) or token fields in the HTMLAffected if No CSRF protection headers or token fields are present in the user management responses
If the device is a Brickcom camera from the affected models and the user management interface lacks anti-CSRF tokens, the environment is vulnerable to CVE-2013-3690.
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 firmware to a version newer than 3.1.0.8 which should include CSRF protection, or implement anti-CSRF tokens in all user management forms and validate them server-side.
- 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-3690 — 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-3690 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