CVE-2019-10220: Path Traversal

Published Nov 27, 2019
·
Updated

Last updated 25 April 2025

Other sources

Linux kernel CIFS implementation, version 4.9.0 is vulnerable to a relative paths injection in directory entry lists.

— Launchpad

Affected Software

60 affected componentsFixes available
Linux Linux kernel>=2.6.12<3.16.81
Linux Linux kernel>=3.17<4.4.208
Linux Linux kernel>=4.5<4.9.208
Linux Linux kernel>=4.10<4.14.162
Linux Linux kernel>=4.15<4.19.93
Linux Linux kernel>=4.20<5.3.8
Debian Debian Linux=8.0
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=19.04
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.22-16.12.25-1
ubuntu/linux-aws<4.4.0-1061.65
4.4.0-1061.65
ubuntu/linux-azure<4.15.0-1071.76~14.04.1
4.15.0-1071.76~14.04.1
ubuntu/linux-lts-xenial<4.4.0-173.203~14.04.1
4.4.0-173.203~14.04.1
ubuntu/linux*
ubuntu/linux<4.4.0-173.203
4.4.0-173.203
ubuntu/linux-aws<4.4.0-1101.112
4.4.0-1101.112
ubuntu/linux-aws-hwe<4.15.0-1060.62~16.04.1
4.15.0-1060.62~16.04.1
ubuntu/linux-azure<4.15.0-1071.76
4.15.0-1071.76
ubuntu/linux-gcp<4.15.0-1055.59
4.15.0-1055.59
ubuntu/linux-hwe<4.15.0-88.88~16.04.1
4.15.0-88.88~16.04.1
ubuntu/linux-kvm<4.4.0-1065.72
4.4.0-1065.72
ubuntu/linux-oracle<4.15.0-1033.36~16.04.1
4.15.0-1033.36~16.04.1
ubuntu/linux-raspi2<4.4.0-1128.137
4.4.0-1128.137
ubuntu/linux-snapdragon<4.4.0-1132.140
4.4.0-1132.140
ubuntu/linux-hwe-edge*
ubuntu/linux-fips<4.4.0-1028.33
4.4.0-1028.33
ubuntu/linux-fips*
ubuntu/linux<4.15.0-88.88
4.15.0-88.88
ubuntu/linux-aws<4.15.0-1060.62
4.15.0-1060.62
ubuntu/linux-aws-5.0<5.0.0-1023.26~18.04.1
5.0.0-1023.26~18.04.1
ubuntu/linux-azure<5.0.0-1028.30~18.04.1
5.0.0-1028.30~18.04.1
ubuntu/linux-azure-5.3<5.3.0-1008.9~18.04.1
5.3.0-1008.9~18.04.1
ubuntu/linux-gcp<5.0.0-1028.29~18.04.1
5.0.0-1028.29~18.04.1
ubuntu/linux-gcp-5.3<5.3.0-1009.10~18.04.1
5.3.0-1009.10~18.04.1
ubuntu/linux-gke-4.15<4.15.0-1052.55
4.15.0-1052.55
ubuntu/linux-gke-5.0<5.0.0-1027.28~18.04.1
5.0.0-1027.28~18.04.1
ubuntu/linux-hwe<5.3.0-26.28~18.04.1
5.3.0-26.28~18.04.1
ubuntu/linux-hwe-edge<5.3.0-24.26~18.04.2
5.3.0-24.26~18.04.2
ubuntu/linux-kvm<4.15.0-1053.53
4.15.0-1053.53
ubuntu/linux-oem<4.15.0-1073.83
4.15.0-1073.83
ubuntu/linux-oem-osp1<5.0.0-1033.38
5.0.0-1033.38
ubuntu/linux-oracle<4.15.0-1033.36
4.15.0-1033.36
ubuntu/linux-oracle-5.0<5.0.0-1009.14~18.04.1
5.0.0-1009.14~18.04.1
ubuntu/linux-raspi2<4.15.0-1055.59
4.15.0-1055.59
ubuntu/linux-snapdragon<4.15.0-1072.79
4.15.0-1072.79
ubuntu/linux-azure-edge*
ubuntu/linux-gcp-edge*
ubuntu/linux-aws-fips<4.15.0-2018.18
4.15.0-2018.18
ubuntu/linux-azure-fips<4.15.0-2006.7
4.15.0-2006.7
ubuntu/linux-aws-fips*
ubuntu/linux-azure-fips*
ubuntu/linux-gcp-fips*
ubuntu/linux-azure-fde*
ubuntu/linux-gke*
ubuntu/linux-raspi2*
ubuntu/linux-intel-iot-realtime*
ubuntu/linux-realtime*
ubuntu/linux-riscv*
ubuntu/linux-raspi-realtime*
ubuntu/linux-vmware*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.22-1Fixed in 6.12.25-1
  2. Upgrade

    Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.

    Fixed in 4.4.0-1061.65
  3. Upgrade

    Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.

    Fixed in 4.15.0-1071.76~14.04.1
  4. Upgrade

    Upgrade ubuntu/linux-lts-xenial to a version that resolves this vulnerability.

    Fixed in 4.4.0-173.203~14.04.1
  5. Upgrade

    Upgrade ubuntu/linux to a version that resolves this vulnerability.

    Fixed in 4.4.0-173.203
  6. Upgrade

    Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.

    Fixed in 4.4.0-1101.112
  7. Upgrade

    Upgrade ubuntu/linux-aws-hwe to a version that resolves this vulnerability.

    Fixed in 4.15.0-1060.62~16.04.1
  8. Upgrade

    Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.

    Fixed in 4.15.0-1071.76
  9. Upgrade

    Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.

    Fixed in 4.15.0-1055.59
  10. Upgrade

    Upgrade ubuntu/linux-hwe to a version that resolves this vulnerability.

    Fixed in 4.15.0-88.88~16.04.1
  11. Upgrade

    Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.

    Fixed in 4.4.0-1065.72
  12. Upgrade

    Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.

    Fixed in 4.15.0-1033.36~16.04.1
  13. Upgrade

    Upgrade ubuntu/linux-raspi2 to a version that resolves this vulnerability.

    Fixed in 4.4.0-1128.137
  14. Upgrade

    Upgrade ubuntu/linux-snapdragon to a version that resolves this vulnerability.

    Fixed in 4.4.0-1132.140
  15. Upgrade

    Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.

    Fixed in 4.4.0-1028.33
  16. Upgrade

    Upgrade ubuntu/linux to a version that resolves this vulnerability.

    Fixed in 4.15.0-88.88
  17. Upgrade

    Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.

    Fixed in 4.15.0-1060.62
  18. Upgrade

    Upgrade ubuntu/linux-aws-5.0 to a version that resolves this vulnerability.

    Fixed in 5.0.0-1023.26~18.04.1
  19. Upgrade

    Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.

    Fixed in 5.0.0-1028.30~18.04.1
  20. Upgrade

    Upgrade ubuntu/linux-azure-5.3 to a version that resolves this vulnerability.

    Fixed in 5.3.0-1008.9~18.04.1
  21. Upgrade

    Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.

    Fixed in 5.0.0-1028.29~18.04.1
  22. Upgrade

    Upgrade ubuntu/linux-gcp-5.3 to a version that resolves this vulnerability.

    Fixed in 5.3.0-1009.10~18.04.1
  23. Upgrade

    Upgrade ubuntu/linux-gke-4.15 to a version that resolves this vulnerability.

    Fixed in 4.15.0-1052.55
  24. Upgrade

    Upgrade ubuntu/linux-gke-5.0 to a version that resolves this vulnerability.

    Fixed in 5.0.0-1027.28~18.04.1
  25. Upgrade

    Upgrade ubuntu/linux-hwe to a version that resolves this vulnerability.

    Fixed in 5.3.0-26.28~18.04.1
  26. Upgrade

    Upgrade ubuntu/linux-hwe-edge to a version that resolves this vulnerability.

    Fixed in 5.3.0-24.26~18.04.2
  27. Upgrade

    Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.

    Fixed in 4.15.0-1053.53
  28. Upgrade

    Upgrade ubuntu/linux-oem to a version that resolves this vulnerability.

    Fixed in 4.15.0-1073.83
  29. Upgrade

    Upgrade ubuntu/linux-oem-osp1 to a version that resolves this vulnerability.

    Fixed in 5.0.0-1033.38
  30. Upgrade

    Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.

    Fixed in 4.15.0-1033.36
  31. Upgrade

    Upgrade ubuntu/linux-oracle-5.0 to a version that resolves this vulnerability.

    Fixed in 5.0.0-1009.14~18.04.1
  32. Upgrade

    Upgrade ubuntu/linux-raspi2 to a version that resolves this vulnerability.

    Fixed in 4.15.0-1055.59
  33. Upgrade

    Upgrade ubuntu/linux-snapdragon to a version that resolves this vulnerability.

    Fixed in 4.15.0-1072.79
  34. Upgrade

    Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.

    Fixed in 4.15.0-2018.18
  35. Upgrade

    Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.

    Fixed in 4.15.0-2006.7

Event History

Nov 27, 2019
CVE Published
via MITRE·03:30 PM
Data Sourced
via MITRE·03:30 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·04:15 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What are the potential impacts of CVE-2019-10220?

CVE-2019-10220 can lead to unauthorized access or manipulation of directory entry lists due to relative path injection.

2

Which versions of the Linux kernel are affected by CVE-2019-10220?

CVE-2019-10220 affects Linux kernel versions between 2.6.12 and 5.3.8, along with specific versions of Debian and Ubuntu Linux.

3

How can I remediate CVE-2019-10220?

To fix CVE-2019-10220, upgrade the Linux kernel to versions 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.119-1, 6.12.10-1, or 6.12.11-1.

4

What types of systems are typically vulnerable to CVE-2019-10220?

Systems running affected versions of the Linux kernel, particularly those using CIFS for file sharing, are vulnerable to CVE-2019-10220.

5

Is CVE-2019-10220 a confirmed vulnerability?

Yes, CVE-2019-10220 has been officially documented and recognized as a vulnerability affecting the Linux CIFS implementation.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203