CVE-2018-6198
published 2018-01-25CVE-2018-6198: w3m through 0.5.3 does not properly handle temporary files when the ~/.w3m directory is unwritable, which allows a local attacker to craft a symlink attack to…
PriorityP421medium4.7CVSS 3.0
AVLACHPRLUINSUCNIHAN
EPSS
0.40%
32.0th percentile
w3m through 0.5.3 does not properly handle temporary files when the ~/.w3m directory is unwritable, which allows a local attacker to craft a symlink attack to overwrite arbitrary files.
Affected
12 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| canonical | ubuntu_linux | — | — |
| canonical | ubuntu_linux | — | — |
| canonical | ubuntu_linux | — | — |
| canonical | ubuntu_linux | — | — |
| debian | w3m | < w3m 0.5.3-36 (bookworm) | w3m 0.5.3-36 (bookworm) |
| tats | w3m | <= 0.5.3 | — |
| tats | w3m | >= 0 < 0.5.3-36 | 0.5.3-36 |
| tats | w3m | >= 0 < 0.5.3-36 | 0.5.3-36 |
| tats | w3m | >= 0 < 0.5.3-36 | 0.5.3-36 |
| tats | w3m | >= 0 < 0.5.3-36 | 0.5.3-36 |
| tats | w3m | >= 0 < 0.5.3-15ubuntu0.2 | 0.5.3-15ubuntu0.2 |
| tats | w3m | >= 0 < 0.5.3-26ubuntu0.2 | 0.5.3-26ubuntu0.2 |
CVSS provenance
nvdv3.04.7MEDIUMCVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
nvdv2.03.3LOWAV:L/AC:M/Au:N/C:N/I:P/A:P
osv7.5HIGH
vendor_ubuntu7.5HIGH
vendor_debian4.7LOW
vendor_redhat4.7MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-gvrg-2xvq-7j38: w3m through 0
ghsa_unreviewed·2022-05-13
CVE-2018-6198 [MEDIUM] CWE-59 GHSA-gvrg-2xvq-7j38: w3m through 0
w3m through 0.5.3 does not properly handle temporary files when the ~/.w3m directory is unwritable, which allows a local attacker to craft a symlink attack to overwrite arbitrary files.
OSV
w3m vulnerabilities
osv·2018-02-01·CVSS 7.5
CVE-2018-6196 [HIGH] w3m vulnerabilities
w3m vulnerabilities
It was discovered that w3m incorrectly handled certain inputs.
An attacker could possibly use this to cause a denial of service.
(CVE-2018-6196, CVE-2018-6197)
It was discovered that w3m incorrectly handled temporary files.
An attacker could possibly use this to overwrite arbitrary files.
(CVE-2018-6198)
OSV
CVE-2018-6198: w3m through 0
osv·2018-01-25·CVSS 4.7
CVE-2018-6198 [MEDIUM] CVE-2018-6198: w3m through 0
w3m through 0.5.3 does not properly handle temporary files when the ~/.w3m directory is unwritable, which allows a local attacker to craft a symlink attack to overwrite arbitrary files.
Ubuntu
w3m vulnerabilities
vendor_ubuntu·2018-02-01·CVSS 7.5
CVE-2018-6196 [HIGH] w3m vulnerabilities
Title: w3m vulnerabilities
Summary: Several security issues were fixed in w3m.
USN-3555-2 fixed vulnerabilities in w3m. This update
provides the corresponding update for Ubuntu 12.04 ESM.
Original advisory details:
It was discovered that w3m incorrectly handled certain inputs.
An attacker could possibly use this to cause a denial of service.
(CVE-2018-6196, CVE-2018-6197)
It was discovered that w3m incorrectly handled temporary files.
An attacker could possibly use this to overwrite arbitrary files.
(CVE-2018-6198)
Instructions: In general, a standard system update will make all the necessary changes.
Ubuntu
w3m vulnerabilities
vendor_ubuntu·2018-02-01·CVSS 7.5
CVE-2018-6196 [HIGH] w3m vulnerabilities
Title: w3m vulnerabilities
Summary: Several security issues were fixed in w3m.
It was discovered that w3m incorrectly handled certain inputs.
An attacker could possibly use this to cause a denial of service.
(CVE-2018-6196, CVE-2018-6197)
It was discovered that w3m incorrectly handled temporary files.
An attacker could possibly use this to overwrite arbitrary files.
(CVE-2018-6198)
Instructions: In general, a standard system update will make all the necessary changes.
Red Hat
w3m: insecure temporary files creation when ~/.w3m is unwritable
vendor_redhat·2018-01-23·CVSS 4.7
CVE-2018-6198 [MEDIUM] CWE-377 w3m: insecure temporary files creation when ~/.w3m is unwritable
w3m: insecure temporary files creation when ~/.w3m is unwritable
w3m through 0.5.3 does not properly handle temporary files when the ~/.w3m directory is unwritable, which allows a local attacker to craft a symlink attack to overwrite arbitrary files.
Package: w3m (Red Hat Enterprise Linux 5) - Will not fix
Package: w3m (Red Hat Enterprise Linux 6) - Will not fix
Package: w3m (Red Hat Enterprise Linux 8) - Not affected
Debian
CVE-2018-6198: w3m - w3m through 0.5.3 does not properly handle temporary files when the ~/.w3m direc...
vendor_debian·2018·CVSS 4.7
CVE-2018-6198 [MEDIUM] CVE-2018-6198: w3m - w3m through 0.5.3 does not properly handle temporary files when the ~/.w3m direc...
w3m through 0.5.3 does not properly handle temporary files when the ~/.w3m directory is unwritable, which allows a local attacker to craft a symlink attack to overwrite arbitrary files.
Scope: local
bookworm: resolved (fixed in 0.5.3-36)
bullseye: resolved (fixed in 0.5.3-36)
forky: resolved (fixed in 0.5.3-36)
sid: resolved (fixed in 0.5.3-36)
trixie: resolved (fixed in 0.5.3-36)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2018-6198 w3m: insecure temporary files creation when ~/.w3m is unwritable [fedora-all]
bugzilla·2018-01-26·CVSS 4.7
CVE-2018-6198 [MEDIUM] CVE-2018-6198 w3m: insecure temporary files creation when ~/.w3m is unwritable [fedora-all]
CVE-2018-6198 w3m: insecure temporary files creation when ~/.w3m is unwritable [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supp
Bugzilla
CVE-2018-6198 w3m: insecure temporary files creation when ~/.w3m is unwritable
bugzilla·2018-01-26·CVSS 4.7
CVE-2018-6198 [MEDIUM] CVE-2018-6198 w3m: insecure temporary files creation when ~/.w3m is unwritable
CVE-2018-6198 w3m: insecure temporary files creation when ~/.w3m is unwritable
A flaw was found in w3m 0.5.3-34. When ~/.w3m is unwritable, w3m uses /tmp in an insecure fashion, which allows a local attacker to craft a symlink attack to overwrite arbitrary files.
Upstream patch:
https://github.com/tats/w3m/commit/18dcbadf2771cdb0c18509b14e4e73505b242753
Discussion:
Created w3m tracking bugs for this issue:
Affects: epel-7 [bug 1539130]
Affects: fedora-all [bug 1539129]
---
Fixed for all the requested releases.
Bugzilla
CVE-2018-6198 w3m: insecure temporary files creation when ~/.w3m is unwritable [epel-7]
bugzilla·2018-01-26·CVSS 4.7
CVE-2018-6198 [MEDIUM] CVE-2018-6198 w3m: insecure temporary files creation when ~/.w3m is unwritable [epel-7]
CVE-2018-6198 w3m: insecure temporary files creation when ~/.w3m is unwritable [epel-7]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-7.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following template to for
http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00028.htmlhttp://www.securityfocus.com/bid/102855https://bugs.debian.org/888097https://github.com/tats/w3m/commit/18dcbadf2771cdb0c18509b14e4e73505b242753https://salsa.debian.org/debian/w3m/commit/18dcbadf2771cdb0c18509b14e4e73505b242753https://usn.ubuntu.com/3555-1/https://usn.ubuntu.com/3555-2/http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00028.htmlhttp://www.securityfocus.com/bid/102855https://bugs.debian.org/888097https://github.com/tats/w3m/commit/18dcbadf2771cdb0c18509b14e4e73505b242753https://salsa.debian.org/debian/w3m/commit/18dcbadf2771cdb0c18509b14e4e73505b242753https://usn.ubuntu.com/3555-1/https://usn.ubuntu.com/3555-2/
2018-01-25
Published