CVE-2019-10197
CVE-2019-10197 Vulnerability Analysis & Exploit Intelligence
A flaw was found in samba versions 4.9.x up to 4.9.13, samba 4.10.x up to 4.10.8 and samba 4.11.x up to 4.11.0rc3, when certain parameters were set in the samba configuration file. An unauthenticated attacker could use this flaw to escape the shared directory and access the contents of directories outside the share.
Published Updated Sources: cvelistV5, redhat
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
3%
chance of exploitation in 30 days
CVSS base
6.5
MEDIUM
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 6.5 | CVSS 3.0 | MEDIUM | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-22
References
15 on the record
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10197
x_refsource_CONFIRM
- www.samba.org/samba/security/CVE-2019-10197.html
x_refsource_MISC
- security.netapp.com/advisory/ntap-20190903-0001/
x_refsource_CONFIRM
- usn.ubuntu.com/4121-1/
vendor-advisory, x_refsource_UBUNTU
- seclists.org/bugtraq/2019/Sep/4
mailing-list, x_refsource_BUGTRAQ
- www.debian.org/security/2019/dsa-4513
vendor-advisory, x_refsource_DEBIAN
- lists.opensuse.org/opensuse-security-announce/2019-09/msg00045.html
vendor-advisory, x_refsource_SUSE
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/M7NYIUZOCIDXWXGWMZ7O5Z7OJ6IX7EAB/
vendor-advisory, x_refsource_FEDORA
Elsewhere on this site
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.