CVE-2021-33393: n/a vulnerability

CVE-2021-33393: lfs/backup in IPFire 2.25-core155 does not ensure that /var/ipfire/backup/bin/backup.pl is owned by the roo...

lfs/backup in IPFire 2.25-core155 does not ensure that /var/ipfire/backup/bin/backup.pl is owned by the root account. It might be owned by an unprivileged account, which could potentially be used to install a Trojan horse backup.pl script that is later executed by root. Similar problems with the ownership/permissions of other files may be present as well.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 3, 2024, 23:50 UTC (UTC+00:00)

Security readout for executives and security teams

IPFire 2.25-core155 may leave a backup script owned by a non-root account. If that happens, a lower-privileged user could tamper with the script and have it run later with root privileges. For a firewall platform, that makes this operationally serious even though no CVSS score is provided. Likely exposure is limited to IPFire 2.25-core155 systems with the affected backup package state. Validate actual file ownership and permissions because the vulnerability depends on whether backup.pl, and possibly related files, are writable or owned by non-root users. Treat this as a high-priority firewall hygiene issue. The main risk is root-level compromise of a security appliance if file ownership is wrong. Prioritize inventory, upgrade status, and ownership validation before broader forensic work. Mitigation focus: Review the IPFire commit and vendor guidance for the corrected backup package behavior.; Upgrade affected IPFire 2.25-core155 systems to a fixed vendor-supported release.; Ensure backup.pl and related backup files are owned by root with restrictive permissions..

Prepared: Jun 2, 2026, 19:36 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-33393 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jun 9, 2021, 21:25 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://github.com/MucahitSaratar/ipfire-2-25-auth-rceCVE reference · x_refsource_MISC
https://github.com/ipfire/ipfire-2.x/commit/6769d909306d7bdc43d64598872126fcf1b217f6CVE reference · x_refsource_MISC
https://github.com/ipfire/ipfire-2.x/commits/master?since=2021-05-17&until=2021-05-17CVE reference · x_refsource_MISC

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.