Skip to content
Noroxi
CVE-2004-2771· NVD / CVE Program· CNA redhat

The expand function in fio.c in Heirloom mailx 12.5 and earlier and BSD mailx 8.1.2 and earlier allows remote attackers to execute arbitrary

The expand function in fio.c in Heirloom mailx 12.5 and earlier and BSD mailx 8.1.2 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in an email address.

HighCVSS 7.5 · v2.0—No exploit Fix available
Published
Dec 24, 2014
Updated
Sep 23, 2026
EPSS
6.9% · 94th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

32

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
2 / 30 · 6.9%

Affected systems

VendorProduct
heirloommailx
oraclelinux
redhatenterprise linux
bsd mailx projectbsd mailx

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • bsd mailx project bsd mailxup to 8.1.2 inclusive
  • heirloom mailxup to 12.5 inclusive
  • oracle linux6
  • oracle linux7
  • redhat enterprise linux6.0
  • redhat enterprise linux7.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12bsd-mailxbefore 8.1.2-0.20071201cvs-18.1.2-0.20071201cvs-1
Debian:6.0heirloom-mailxbefore 12.4-2+deb6u112.4-2+deb6u1
Debian:7heirloom-mailxbefore 12.5-2+deb7u112.5-2+deb7u1
openSUSE:Tumbleweedmailxbefore 12.5-24.412.5-24.4
Red Hat:enterprise_linux:6::clientmailxbefore 0:12.4-8.el6_60:12.4-8.el6_6
Red Hat:enterprise_linux:6::clientmailx-debuginfobefore 0:12.4-8.el6_60:12.4-8.el6_6
Red Hat:enterprise_linux:7::clientmailxbefore 0:12.5-12.el7_00:12.5-12.el7_0
Red Hat:enterprise_linux:7::clientmailx-debuginfobefore 0:12.5-12.el7_00:12.5-12.el7_0

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:bsd-mailx8.1.2-0.20071201cvs-1 · Debian:12Package registry (OSV)
debian:heirloom-mailx12.4-2+deb6u1 · Debian:6.0Package registry (OSV)
opensuse:mailx12.5-24.4 · openSUSE:TumbleweedPackage registry (OSV)
red hat:mailx0:12.4-8.el6_6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:mailx-debuginfo0:12.4-8.el6_6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records