# CVE-2013-0157: Information disclosure in n/a > Local attackers can determine the existence of restricted directories by observing error messages from mount and umount commands. - **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 21 Jan 2014 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2013-0157, GHSA-5f9c-xx25-xwrv, RHSA-2013:0517, UBUNTU-CVE-2013-0157 ## What is CVE-2013-0157? CVE-2013-0157 is a low-severity vulnerability in n/a, published on 21 Jan 2014. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description (a) mount and (b) umount in util-linux 2.14.1, 2.17.2, and probably other versions allow local users to determine the existence of restricted directories by (1) using the --guess-fstype command-line option or (2) attempting to mount a non-existent device, which generates different error messages depending on whether the directory exists. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2013-0157? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libblkid` | Red Hat:enterprise_linux:6::client | All versions | 0:2.17.2-12.9.el6 | | `libblkid-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.17.2-12.9.el6 | | `libuuid` | Red Hat:enterprise_linux:6::client | All versions | 0:2.17.2-12.9.el6 | | `libuuid-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.17.2-12.9.el6 | | `util-linux-ng` | Red Hat:enterprise_linux:6::client | All versions | 0:2.17.2-12.9.el6 | | `util-linux-ng-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.17.2-12.9.el6 | | `uuidd` | Red Hat:enterprise_linux:6::client | All versions | 0:2.17.2-12.9.el6 | | `libblkid` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.17.2-12.9.el6 | | `libblkid-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.17.2-12.9.el6 | | `libuuid` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.17.2-12.9.el6 | | `libuuid-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.17.2-12.9.el6 | | `util-linux-ng` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.17.2-12.9.el6 | | `util-linux-ng-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.17.2-12.9.el6 | | `uuidd` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.17.2-12.9.el6 | | `libblkid` | Red Hat:enterprise_linux:6::server | All versions | 0:2.17.2-12.9.el6 | | `libblkid-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.17.2-12.9.el6 | | `libuuid` | Red Hat:enterprise_linux:6::server | All versions | 0:2.17.2-12.9.el6 | | `libuuid-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.17.2-12.9.el6 | | `util-linux-ng` | Red Hat:enterprise_linux:6::server | All versions | 0:2.17.2-12.9.el6 | | `util-linux-ng-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.17.2-12.9.el6 | | `uuidd` | Red Hat:enterprise_linux:6::server | All versions | 0:2.17.2-12.9.el6 | | `libblkid` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.17.2-12.9.el6 | | `libblkid-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.17.2-12.9.el6 | | `libuuid` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.17.2-12.9.el6 | | `libuuid-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.17.2-12.9.el6 | | `util-linux-ng` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.17.2-12.9.el6 | | `util-linux-ng-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.17.2-12.9.el6 | | `uuidd` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.17.2-12.9.el6 | Products: Kernel Util-Linux. ## How do I fix CVE-2013-0157? Apply the vendor's patch. ## Is CVE-2013-0157 being exploited? There is no known exploitation of CVE-2013-0157 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2015-5224](https://insights.sbomify.com/CVE-2015-5224/): Race condition in n/a (critical 9.8) - [CVE-2018-7738](https://insights.sbomify.com/CVE-2018-7738/): Command injection in n/a (high 7.8) - [CVE-2016-2779](https://insights.sbomify.com/CVE-2016-2779/): Privilege escalation in n/a (high 7.8) - [CVE-2026-13595](https://insights.sbomify.com/CVE-2026-13595/): Util-linux: util-linux: heap use-after-free in libblkid nested partition probing (medium 6.8) - [CVE-2020-21583](https://insights.sbomify.com/CVE-2020-21583/): Command injection in n/a (medium 6.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2013-0157 and fix it if it is affected. What it is: CVE-2013-0157 is a low-severity vulnerability in n/a, published on 21 Jan 2014. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2013-0157 in the wild and no public exploit code. Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2013-0157/ (Markdown: https://insights.sbomify.com/CVE-2013-0157/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2013-0157 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-0157 - OSV: https://osv.dev/vulnerability/CVE-2013-0157 --- From sbomify Insights: https://insights.sbomify.com/CVE-2013-0157/ Summaries are generated and may contain mistakes; the official description above is the record.