CVE-2012-3002
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 · uneditedThe web interface on (1) Foscam and (2) Wansview IP cameras allows remote attackers to bypass authentication, and perform administrative functions or read the admin password, via a direct request to an unspecified URL.
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 confidenceAuthentication bypass vulnerability in the web interface of Foscam and Wansview IP cameras allows remote attackers to access administrative functions or read the admin password by making direct requests to unspecified URLs without any authentication 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 dataall 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
- 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.
-
Identify Foscam or Wansview cameras on the networkScan your network for devices with web interfaces running on typical camera ports (80, 8080, 88, etc.). Use network scanning tools or review DHCP lease tables and network device inventories to identify cameras by their manufacturer signatures or MAC vendor prefixes (Foscam uses specific OUI).Affected if The network contains a Foscam or Wansview H.264 IP camera (Hi3510/11/12 series)
-
Verify the web interface is accessibleAttempt to access the camera's web interface by entering its IP address in a browser. Look for login pages or administrative interfaces that load without requiring credentials.Affected if The camera's web interface loads and responds to HTTP requests on any port
-
Confirm camera model and firmware versionAccess the camera's status or system information page through the web interface or by querying the device via ONVIF, RTSP, or manufacturer-specific API endpoints. Document the exact model number (H.264 Hi3510/11/12 series) and firmware version if displayed.Affected if The device is confirmed as a Foscam or Wansview H.264 Hi3510/11/12 camera of any firmware version
-
Check network exposure of the cameraReview firewall rules, router port forwarding configurations, and access control lists to determine whether the camera's web interface is reachable from outside the local network or from untrusted network segments.Affected if The camera's web interface is accessible from network segments outside the trusted internal network
A user is affected if they have any Foscam or Wansview H.264 Hi3510/11/12 IP camera on their network with an accessible web interface, since all versions of these products contain the authentication bypass vulnerability.
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 dataApply available firmware updates from Foscam and Wansview for affected camera models. If no update is available, isolate cameras on a restricted network segment and disable remote web access.
- 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-2012-3002 — 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-2012-3002 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