CVE-2020-6779
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 · uneditedUse of Hard-coded Credentials in the database of Bosch FSM-2500 server and Bosch FSM-5000 server up to and including version 5.2 allows an unauthenticated remote attacker to log into the database with admin-privileges. This may result in complete compromise of the confidentiality and integrity of the stored data as well as a high availability impact on the database itself. In addition, an attacker may execute arbitrary commands on the underlying operating 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 · high confidenceHard-coded administrative credentials embedded in the database layer of Bosch FSM-2500 and FSM-5000 servers (versions up to 5.2) allow unauthenticated remote attackers to gain full admin access to the database. This grants complete control over stored data and enables arbitrary OS command execution through database functionality.
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.2<= 5.2CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
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 FSM device model and firmware versionAccess the device management interface or check the system information page on the Bosch FSM-2500 or FSM-5000 device. The firmware version is typically displayed in the system settings or about section of the web UI.Affected if The device is a Bosch FSM-2500 or FSM-5000 with firmware version 5.2 or lower.
-
Determine if the database service is network accessibleScan the device's IP address for open database ports (default PostgreSQL port 5432, MySQL port 3306, or the vendor-specific database port). Use a tool like nmap: 'nmap -p 5432,3306 <device_ip>' or check firewall rules.Affected if The database service port is open and reachable from an untrusted network or the internet.
-
Verify database authentication with hard-coded credentialsAttempt to connect to the database service using known default credentials or the hard-coded credentials referenced in the CVE. Check if administrative access is granted without credential changes.Affected if The database accepts authentication with default or hard-coded administrative credentials and grants full admin privileges.
-
Check for unauthorized database user accountsQuery the database for user accounts: 'SELECT username FROM pg_user;' for PostgreSQL or 'SELECT user FROM mysql.user;' for MySQL. Look for unexpected administrative accounts beyond those documented.Affected if Unexpected administrative user accounts exist in the database, especially accounts not created by your organization.
The environment is affected if the Bosch FSM-2500 or FSM-5000 device runs firmware version 5.2 or lower AND the database service is network-accessible, allowing exploitation of the hard-coded credentials for unauthorized admin access.
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 dataImmediately restrict network exposure of affected devices, contact Bosch for patched firmware beyond version 5.2, and implement compensating controls such as network segmentation and firewall rules until the vendor patch can be applied.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6779 — 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-6779 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