An issue was discovered on MOBOTIX S14 MX-V4.2.1.61 devices.
An issue was discovered on MOBOTIX S14 MX-V4.2.1.61 devices. /admin/access accepts a request to set the "aaaaa" password, considered insecure for some use cases, from a user.
- Published
- Feb 9, 2019
- Updated
- Jun 16, 2026
- EPSS
- 1.3% · 71th percentile
- CWE
- CWE-521
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.3%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- mobotix s14 firmwaremx-v4.2.1.61
Same product
mobotix: all recordsOther highest-scoring records for the same primary product.
- CVE-2009-5154An issue was discovered on MOBOTIX S14 MX-V4.2.1.61 devices.40Plan
- CVE-2019-12502There is a lack of CSRF countermeasures on MOBOTIX S14 MX-V4.2.1.61 cameras, as demonstrated by adding an admin account via the /admin/acces35Monitor
- CVE-2019-7675An issue was discovered on MOBOTIX S14 MX-V4.2.1.61 devices.30Monitor
- CVE-2019-7673An issue was discovered on MOBOTIX S14 MX-V4.2.1.61 devices.30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-521 · Weak Password RequirementsCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Brute ForceCAPEC-112High
- Dictionary-based Password AttackCAPEC-16likelihood: Medium · High
- Password Brute ForcingCAPEC-49likelihood: Medium · High
- KerberoastingCAPEC-509High
- Rainbow Table Password CrackingCAPEC-55likelihood: Medium · Medium
- Remote Services with Stolen CredentialsCAPEC-555Very High
- Windows Admin Shares with Stolen CredentialsCAPEC-561
- Password SprayingCAPEC-565likelihood: High · High
ATT&CK techniques
- Remote ServicesT1021
- Remote Services:SMB/Windows Admin SharesT1021.002
- Valid Accounts:Default AccountsT1078.001
- Brute ForceT1110
- Brute Force:Password GuessingT1110.001
- Brute Force:Password CrackingT1110.002
- Brute Force:Password SprayingT1110.003
- Email Collection:Remote Email CollectionT1114.002
- External Remote ServicesT1133
- Steal or Forge Kerberos Tickets:KerberoastingT1558.003
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.