CVE-2013-1444: A certain Debian patch for txt2man 1.5.5, as used in txt2man 1.5.5-2, 1.5.5-4, and others, allows local users

Routine

LOW 3.3WATCHLISTDOWNGRADEDOWNGRADE

CVE-2013-1444 is a low-severity flaw (CVSS 3.3) affecting txt2man, txt2man. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A certain Debian patch for txt2man 1.5.5, as used in txt2man 1.5.5-2, 1.5.5-4, and others, allows local users to overwrite arbitrary files via a symlink attack on /tmp/2222.

Why this priority

On your watchlist

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

Risk facts

CVSS score	3.3 (Low)
EPSS exploit chance	0.3% (top 72%)
CISA exploited list	No
Weakness	CWE-59
Published	2013-09-30
Last modified	2026-06-16

Publisher (CNA): Debian GNU/Linux · Vendor: debian · marc vertes

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

Am I affected?

Timeline

2013-09-30 22:55 UTCPublished CVE record published
2026-06-16 23:51 UTCUpdated Record last modified

debian txt2man DOWNGRADE

Affected: 1.5.5-2 · 1.5.5-4

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.5.5-2

1. Check installed version

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

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

apt-cache madison txt2man sudo apt install txt2man=<VERSION_BEFORE_1.5.5-2> sudo apt-mark hold txt2man

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

dnf --showduplicates list txt2man sudo dnf downgrade txt2man-<VERSION_BEFORE_1.5.5-2> sudo dnf versionlock add txt2man

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.

marc vertes txt2man DOWNGRADE

Affected: 1.5.5

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.5.5

1. Check installed version

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

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

apt-cache madison txt2man sudo apt install txt2man=<VERSION_BEFORE_1.5.5> sudo apt-mark hold txt2man

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

dnf --showduplicates list txt2man sudo dnf downgrade txt2man-<VERSION_BEFORE_1.5.5> sudo dnf versionlock add txt2man

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-2013-1444?

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

Is CVE-2013-1444 being exploited?

CVE-2013-1444 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-2013-1444 affect?

CVE-2013-1444 affects txt2man, txt2man. Severity is low (CVSS 3.3). A certain Debian patch for txt2man 1.5.5, as used in txt2man 1.5.5-2, 1.5.5-4, and others, allows local users to overwrite arbitrary files via a symlink attack on /tmp/2222.

How urgent is CVE-2013-1444?

Priority 23/100. On your watchlist

Software pages

Debian vulnerabilities

References

← Back to latest CVEs