Menu

Star on GitHub · 3.2k

CVE-2000-0270

3.6 · LOW

The make-temp-name Lisp function in Emacs 20 creates temporary files with predictable names, which allows attackers to conduct a symlink attack.

Published Apr 18, 2000gnuEPSS 0.35%

Overview

CVE-2000-0270 is a low-severity vulnerability affecting gnu emacs. It was published on April 18, 2000 and has a CVSS 2.0 base score of 3.6 (LOW).

This vulnerability has a CVSS 2.0 base score of 3.6, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

The make-temp-name Lisp function in Emacs 20 creates temporary files with predictable names, which allows attackers to conduct a symlink attack.

Remediation

Check the references section for vendor advisories and patches from gnu. Update emacs to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2000-0270?

CVE-2000-0270 is a low-severity vulnerability affecting gnu emacs. It was published on April 18, 2000 and has a CVSS 2.0 base score of 3.6 (LOW).

How severe is CVE-2000-0270?

This vulnerability has a CVSS 2.0 base score of 3.6, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2000-0270?

Check the references section for vendor advisories and patches from gnu. Update emacs to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2000-0270?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2000-0270 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2000

View all