Skip to content
Fencer Intel
low 3.7

CVE-2010-1161 json

Race condition in GNU nano before 2.2.4, when run by root to edit a file that is not owned by root, allows local user-assisted attackers to…

published 16y ago modified 4mo ago also EUVD-2010-1191

cvss
3.7
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 20%
public exploits
0
none known

Summary

Race condition in GNU nano before 2.2.4, when run by root to edit a file that is not owned by root, allows local user-assisted attackers to change the ownership of arbitrary files via vectors related to the creation of backup files.

Patch / fix

  • nano Debian 14, Debian 13, Debian 12 2.2.4-1

debian advisories DEBIAN-CVE-2010-1161

  • nano openSUSE Tumbleweed 2.7.1-1.1

opensuse advisories openSUSE-SU-2024:10435-1

Is CVE-2010-1161 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-1161 updated cvss 3.6

nano: multiple file editing insecurities

  • Red Hat Enterprise Linux 4 nano Red Hat Enterprise Linux 5 nano
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 6 nano
    affected: no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 3.7 AV:L/AC:H/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.