Unauthenticated command execution via crafted LaTeX input
Published Mar 1, 2021 · Updated Aug 3, 2024
OS command injection in EPrints 3.4.2 allows remote attackers to execute operating-system commands through crafted LaTeX input. The cgi/cal endpoint incorporates the attacker-controlled year value into LaTeX content whose processing permits embedded OS commands. No authentication or user interaction is required, and successful exploitation provides arbitrary command execution on the repository host.
Summary
What happened
OS command injection in EPrints 3.4.2 allows remote attackers to execute operating-system commands through crafted LaTeX input. The cgi/cal endpoint incorporates the attacker-controlled year value into LaTeX content whose processing permits embedded OS commands. No authentication or user interaction is required, and successful exploitation provides arbitrary command execution on the repository host.
The record
- CVE
- CVE-2021-26476
- Published
- Mar 1, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-78, T1059, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 1, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- EPrints security review proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo