Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2017-8225: Authentication bypass and credential disclosure in WIFICAM P2P IP cameras

Published Apr 25, 2017 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3
EPSS35.4%98th percentile
CISA KEVNoNot listed
In the wildReported2 exploitation records in Mallory
Vendor
Wificam
IdentifiersCVE-2017-8225CWE-287

CVE-2017-8225 is an authentication bypass in the OEM-customized, GoAhead-based HTTP server used by Wireless IP Camera (P2P) WIFICAM devices. Access checks for credential-bearing camera configuration files can be bypassed by supplying empty loginuse and loginpas URI parameters. An unauthenticated attacker can retrieve camera credentials and configured FTP and SMTP account details. The flaw originates in OEM customizations rather than GoAhead itself. Combining the disclosed credentials with a separate authenticated FTP configuration command-injection vulnerability enables unauthenticated remote code execution as root.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

The vulnerability directly exposes sensitive camera configuration data, including camera login credentials and FTP and SMTP account credentials, without authentication. A demonstrated exploit chain uses the recovered credentials to access a separate authenticated command-injection flaw and obtain root-level code execution. CVE-2017-8225 has also been used in IoTroop and Moobot device-compromise campaigns; those observations do not establish that credential disclosure alone provides code execution.

Mitigation

If you can’t patch tonight, do this now.

Immediately disconnect affected cameras from the Internet. Check Point IPS protections were reported to block the infection methods observed in the IoTroop campaign; this is a compensating control, not a correction of the underlying authentication flaw.

Remediation

Patch, then assume compromise.

Disconnect affected cameras from direct Internet exposure immediately. Replace affected firmware or devices with vendor-supported products that correct the custom HTTP-server authentication logic and prevent unauthenticated access to configuration files. Rotate all camera, FTP, SMTP, and other credentials that may have been stored on or used by affected devices.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
WificamWireless Ip Camera (P2p) Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2017-8225 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2017-8225?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2017-8225, the earliest disclosed Sep 8, 2023.
Is there a patch for CVE-2017-8225?
Disconnect affected cameras from direct Internet exposure immediately. Replace affected firmware or devices with vendor-supported products that correct the custom HTTP-server authentication logic and prevent unauthenticated access to configuration files.
What products are affected by CVE-2017-8225?
Wificam Wireless Ip Camera (P2p) Firmware.
How severe is CVE-2017-8225?
CVE-2017-8225 has a CVSS v3 score of 9.8 (Critical) and an EPSS score of 35.4% (98th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+2 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware3Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.