CVE-2018-10328
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 · uneditedMomentum Axel 720P 5.1.8 devices have a hardcoded password of streaming for the appagent account, which allows remote attackers to view the RTSP video stream.
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 confidenceMomentum Axel 720P 5.1.8 IP camera devices contain a hardcoded password 'streaming' for the appagent account. This allows any remote attacker with network access to authenticate to the RTSP (Real Time Streaming Protocol) service and view the video stream without 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 data= 5.1.8CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/C:H/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 Momentum Axel 720P cameras on your networkScan your network for devices with vendor identifier for Momentum or specific MAC address patterns associated with this device model. Check your network device inventory or use Nmap with service detection for RTSP (port 554 typically).Affected if You have any Momentum Axel 720P IP cameras deployed on your network.
-
Check the firmware version of the cameraAccess the camera web interface or use SNMP to query the device firmware version. The exact method depends on your camera management system - check the device metadata or use the vendor's discovery tool.Affected if The firmware version is exactly 5.1.8.
-
Verify if RTSP service is enabled and exposedCheck if port 554 (default RTSP) is open and accessible on the camera. Use a port scan or check your firewall rules for outbound connections to the camera on port 554.Affected if RTSP service is enabled and reachable on the network segment where the camera resides.
-
Confirm the hardcoded credential is validAttempt to authenticate to the RTSP service using the username 'appagent' and password 'streaming'. Use an RTSP client or tool like ffmpeg: rtsp://appagent:streaming@<camera_ip>:554/streamAffected if Authentication succeeds with these hardcoded credentials, confirming the vulnerability is exploitable in your environment.
You are affected if you have Momentum Axel 720P cameras running firmware version 5.1.8 with RTSP service enabled and accessible, where the hardcoded 'streaming' password for the appagent account successfully authenticates to the RTSP stream.
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 dataReplace or retire affected devices as hardcoded credentials cannot be changed by end users. If continued use is required, isolate devices on a restricted network segment and monitor for unauthorized RTSP connections.
- 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-2018-10328 — 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-2018-10328 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