CVE-2020-28973
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 ABUS Secvest wireless alarm system FUAA50000 (v3.01.17) fails to properly authenticate some requests to its built-in HTTPS interface. Someone can use this vulnerability to obtain sensitive information from the system, such as usernames and passwords. This information can then be used to reconfigure or disable the alarm system.
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 · moderate confidenceThe ABUS Secvest FUAA50000 alarm system (v3.01.17) contains an authentication bypass vulnerability in its built-in HTTPS management interface. The flaw allows unauthenticated remote attackers to bypass authentication checks on certain API endpoints, enabling them to extract sensitive credentials including usernames and passwords stored on the device. These credentials can then be used to fully administer the alarm system, allowing attackers to reconfigure or disable security features.
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.01.17CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 the device modelLocate the physical device or check network inventory for ABUS Secvest Wireless Alarm System model FUAA50000Affected if The device model is FUAA50000
-
Check the installed firmware versionAccess the device's web interface or check device documentation for the firmware version. The exact version is typically displayed in the system settings or status page of the alarm system management interfaceAffected if The firmware version is exactly 3.01.17
-
Verify HTTPS management interface accessibilityDetermine if the device's HTTPS management interface is reachable from the network. Check network exposure and firewall rules to see if port 443 (or the configured HTTPS port) is accessibleAffected if The HTTPS management interface is exposed to the network without proper access controls
-
Test API endpoint authentication bypassAttempt to access the API endpoints without providing credentials. The vulnerability allows bypassing authentication on certain API endpoints - check if unauthenticated requests to these endpoints return sensitive data or administrative functionsAffected if API endpoints can be accessed without authentication and return credential data or administrative responses
-
Audit for signs of credential extractionReview any logs, network traffic captures, or configuration change records that might indicate unauthorized access has occurred. Check if credentials or configuration files have been accessed or exportedAffected if Logs or system state show evidence of unauthorized credential access or configuration changes
You are affected if you have an ABUS Secvest FUAA50000 alarm system running firmware version 3.01.17 with its HTTPS management interface network-accessible.
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 vendor firmware updates when available; if no patch exists, implement network segmentation to restrict access to the alarm system's management interface, or replace the device with a supported model. Monitor for unauthorized configuration changes.
- Consultation4.0 h
- Implementation4.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 $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-28973 — 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-2020-28973 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