CVE-2019-3880
MEDIUMCVSS 5.4/10EPSS 3.39%
Last modified
CVE-2019-3880 is a medium-severity vulnerability rated 5.4/10 on the CVSS scale. A flaw was found in the way samba implemented an RPC endpoint emulating the Windows registry service API. An unprivileged attacker could use this flaw to create a new registry hive file anywhere they have unix permissions which could lead to creation of a new file in the Samba share. EPSS estimates a 3.39% chance of exploitation in the next 30 days.
Description
A flaw was found in the way samba implemented an RPC endpoint emulating the Windows registry service API. An unprivileged attacker could use this flaw to create a new registry hive file anywhere they have unix permissions which could lead to creation of a new file in the Samba share. Versions before 4.8.11, 4.9.6 and 4.10.2 are vulnerable.
Metrics
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Samba | Samba | >= 3.2.0, < 4.8.11 |
| Samba | Samba | >= 4.9.0, < 4.9.6 |
| Samba | Samba | >= 4.10.0, < 4.10.2 |
| Debian | Debian Linux | 8.0 |
| Redhat | Gluster Storage | 3.0 |
| Redhat | Enterprise Linux | 7.0 |
| Fedoraproject | Fedora | 28 |
| Fedoraproject | Fedora | 29 |
| Fedoraproject | Fedora | 30 |
| Opensuse | Leap | 42.3 |
References
- http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00050.htmlMailing List, Patch, Third Party Advisory
- http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00106.htmlThird Party Advisory
- https://access.redhat.com/errata/RHSA-2019:1966Third Party Advisory
- https://access.redhat.com/errata/RHSA-2019:1967Third Party Advisory
- https://access.redhat.com/errata/RHSA-2019:2099Third Party Advisory
- https://access.redhat.com/errata/RHSA-2019:3582Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3880Issue Tracking, Mitigation, Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2019/04/msg00013.htmlThird Party Advisory
- https://security.netapp.com/advisory/ntap-20190411-0004/Third Party Advisory
- https://support.f5.com/csp/article/K20804356Third Party Advisory
- https://www.samba.org/samba/security/CVE-2019-3880.htmlMitigation, Patch, Vendor Advisory
- https://www.synology.com/security/advisory/Synology_SA_19_15Third Party Advisory
- https://access.redhat.com/security/cve/cve-2019-3880Mitigation, Third Party Advisory
- http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00050.htmlMailing List, Patch, Third Party Advisory
- http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00106.htmlThird Party Advisory
- https://access.redhat.com/errata/RHSA-2019:1966Third Party Advisory
- https://access.redhat.com/errata/RHSA-2019:1967Third Party Advisory
- https://access.redhat.com/errata/RHSA-2019:2099Third Party Advisory
- https://access.redhat.com/errata/RHSA-2019:3582Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3880Issue Tracking, Mitigation, Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2019/04/msg00013.htmlThird Party Advisory
- https://security.netapp.com/advisory/ntap-20190411-0004/Third Party Advisory
- https://support.f5.com/csp/article/K20804356Third Party Advisory
- https://www.samba.org/samba/security/CVE-2019-3880.htmlMitigation, Patch, Vendor Advisory
- https://www.synology.com/security/advisory/Synology_SA_19_15Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2019-3880?
A flaw was found in the way samba implemented an RPC endpoint emulating the Windows registry service API. An unprivileged attacker could use this flaw to create a new registry hive file anywhere they have unix permissions which could lead to creation of a new file in the Samba share. Versions before 4.8.11, 4.9.6 and 4.10.2 are vulnerable.
How severe is CVE-2019-3880?
CVE-2019-3880 has a CVSS score of 5.4/10 (MEDIUM severity). The EPSS model estimates a 3.39% probability of exploitation in the next 30 days.
How do I fix CVE-2019-3880?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2019
- CVE-2019-3874The SCTP socket buffer used by a userspace application is no…6.5
- CVE-2019-3875A vulnerability was found in keycloak before 6.0.2. The X.50…6.5
- CVE-2019-3876A flaw was found in the /oauth/token/request custom endpoint…6.3
- CVE-2019-3877A vulnerability was found in mod_auth_mellon before v0.14.2.…5.8
- CVE-2019-3878A vulnerability was found in mod_auth_mellon before v0.14.2.…8.1
- CVE-2019-3879It was discovered that in the ovirt's REST API before versio…8.1
- CVE-2019-3881Bundler prior to 2.1.0 uses a predictable path in /tmp/, cre…7.8
- CVE-2019-3882A flaw was found in the Linux kernel's vfio interface implem…5.5
- CVE-2019-3883In 389-ds-base up to version 1.4.1.2, requests are handled b…7.5
- CVE-2019-3884A vulnerability exists in the garbage collection mechanism o…5.4
- CVE-2019-3885A use-after-free flaw was found in pacemaker up to and inclu…3.3
- CVE-2019-3886An incorrect permissions check was discovered in libvirt 4.8…5.4
Are you affected by CVE-2019-3880?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST