CVE-2007-0473: The writeFile function in core/smb4kfileio.cpp in Smb4K before 0.8.0 does not preserve /etc/sudoers permission

Routine

LOW 1.9DOWNGRADE

CVE-2007-0473 is a low-severity flaw (CVSS 1.9) affecting smb4k. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The writeFile function in core/smb4kfileio.cpp in Smb4K before 0.8.0 does not preserve /etc/sudoers permissions across modifications, which allows local users to obtain sensitive information (/etc/sudoers contents) by reading this file.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	1.9 (Low)
EPSS exploit chance	0.4% (top 68%)
CISA exploited list	No
Published	2007-02-03
Last modified	2026-06-16

Publisher (CNA): Canonical Ltd. · Vendor: smb4k

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2007-02-03 23:28 UTCPublished CVE record published
2026-06-16 22:35 UTCUpdated Record last modified

smb4k smb4k DOWNGRADE

Affected: 0.4 · 0.5 · 0.6 · 0.7

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.4

1. Check installed version

apt-cache policy smb4k || rpm -q smb4k || smb4k --version

2. No fixed release: DOWNGRADE to a release before 0.4 (Debian / Ubuntu)

apt-cache madison smb4k sudo apt install smb4k=<VERSION_BEFORE_0.4> sudo apt-mark hold smb4k

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list smb4k sudo dnf downgrade smb4k-<VERSION_BEFORE_0.4> sudo dnf versionlock add smb4k

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2007-0473?

smb4k: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2007-0473 being exploited?

CVE-2007-0473 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2007-0473 affect?

CVE-2007-0473 affects smb4k. Severity is low (CVSS 1.9). The writeFile function in core/smb4kfileio.cpp in Smb4K before 0.8.0 does not preserve /etc/sudoers permissions across modifications, which allows local users to obtain sensitive information (/etc/sudoers contents) by reading this file.

How urgent is CVE-2007-0473?

Priority 15/100. No elevated risk signals yet.

Related CVEs

CVE-2017-8849 HIGH 7.8 UPGRADE MITIGATE smb4k before 2.0.1 allows local users to gain root privileges by leveraging failure to verify arguments to the
CVE-2014-2581 HIGH 7.5 UPGRADE MITIGATE Smb4K before 1.1.1 allows remote attackers to obtain credentials via vectors related to the cuid option in the
CVE-2007-0475 MEDIUM 4.4 DOWNGRADE Multiple stack-based buffer overflows in utilities/smb4k_*.cpp in Smb4K before 0.8.0 allow local users, when p
CVE-2007-0474 LOW 3.3 DOWNGRADE Smb4K before 0.8.0 allow local users, when present on the Smb4K sudoers list, to kill arbitrary processes, rel
CVE-2007-0472 LOW 3.7 DOWNGRADE Multiple race conditions in Smb4K before 0.8.0 allow local users to (1) modify arbitrary files via unspecified

References

← Back to latest CVEs