MariaDBDatabase / datastore
CVE-2023-5157
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 · uneditedA vulnerability was found in MariaDB. An OpenVAS port scan on ports 3306 and 4567 allows a malicious remote client to cause a denial of service.
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 confidenceA denial of service vulnerability exists in MariaDB where an OpenVAS port scan targeting ports 3306 and 4567 can cause the database service to crash or become unresponsive. The vulnerability is triggered by malformed network packets during the scan process, allowing a remote attacker to disrupt database availability without authentication.
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
MariaDBDatabase / datastore
< 10.3.36>= 10.4.0, < 10.4.26>= 10.5.0, < 10.5.17>= 10.6.0, < 10.6.9>= 10.7.0, < 10.7.5>= 10.8.0, < 10.8.4
FedoraOperating system
= 38
Enterprise LinuxOperating system
= 8.0= 9.0
Enterprise Linux EusOperating system
= 8.6= 8.8= 9.0= 9.2
Enterprise Linux For Arm 64Operating system
= 8.0_aarch64= 9.0_aarch64
Enterprise Linux For Arm 64 EusOperating system
= 8.8_aarch64
Enterprise Linux For Ibm Z SystemsOperating system
= 8.0_s390x= 9.0_s390x= 9.2_s390x
Enterprise Linux For Ibm Z Systems EusOperating system
= 8.6_s390x= 8.8_s390x= 9.2_s390xCVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Check installed MariaDB versionRun 'mysql --version' or 'mariadb --version' to get the exact version number. On Red Hat/Fedora, also check 'rpm -qa | grep mariadb' or 'rpm -qa | grep mysql'Affected if The version falls into any of these ranges: < 10.3.36; >= 10.4.0, < 10.4.26; >= 10.5.0, < 10.5.17; >= 10.6.0, < 10.6.9; >= 10.7.0, < 10.7.5; >= 10.8.0, < 10.8.4
-
Verify MariaDB service is running and listeningRun 'netstat -tlnp | grep -E "3306|4567"' or 'ss -tlnp | grep -E "3306|4567"' to check if MariaDB ports are actively listeningAffected if Ports 3306 or 4566 are in LISTEN state, indicating the database is accepting network connections
-
Assess network exposure of database portsCheck firewall rules with 'firewall-cmd --list-all' (Fedora/RHEL 7+) or 'iptables -L -n' to see if ports 3306 and 4567 are open to untrusted networks. Also verify with 'nmap -p 3306,4567 <your-external-ip>' from an untrusted network if accessibleAffected if Ports 3306 or 4567 are open to network segments that contain untrusted or internet-facing clients
-
Confirm service accessibilityAttempt a basic connection test with 'mysql -h 127.0.0.1 -P 3306 -u root -p' or verify the port responds to raw connection attempts using 'nc -v 127.0.0.1 3306'Affected if The ports accept TCP connections, meaning a remote attacker could send malformed packets to trigger the crash
Your environment is affected if you run a vulnerable MariaDB version (per the ranges above) AND have ports 3306 or 4567 exposed to untrusted network access where an attacker could send malformed scan packets.
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.
dbcve · scoped10.3.3610.4.2610.5.17
Restrict network access to MariaDB ports 3306 and 4567 using firewall rules or network segmentation to prevent untrusted remote clients from scanning or connecting. Consider upgrading MariaDB to a patched version once available.
Upgrade to MariaDB 10.3.36+, 10.4.26+, 10.5.17+, or 10.6.9+ (whichever minimal version is appropriate for your current major branch)
- 1. Identify the currently installed MariaDB version using: `rpm -qa | grep mariadb` or `mysql --version`
- 2. Back up all databases using `mysqldump --all-databases > backup.sql`
- 3. Stop the MariaDB service: `systemctl stop mariadb` or `systemctl stop mysqld`
- 4. Update MariaDB packages using your package manager: `dnf update mariadb` (Fedora/RHEL) or `apt-get update && apt-get install mariadb-server` (Debian/Ubuntu)
- 5. Verify the new version meets the fixed release criteria: 10.3.36+, 10.4.26+, 10.5.17+, or 10.6.9+
- 6. Start the MariaDB service: `systemctl start mariadb`
- 7. Run mysql_upgrade to ensure all system tables are current: `mysql_upgrade -u root -p`
- 8. Restart the MariaDB service to apply all changes: `systemctl restart mariadb`
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in MariaDB
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5157 — 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-2023-5157 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