LiveActive security incident?Get immediate response
CVE Record

CVE-2013-2777: sudo before 1.7.10p5 and 1.8.x before 1.8.6p6, when the tty_tickets option is enabled, does not properly va...

sudo before 1.7.10p5 and 1.8.x before 1.8.6p6, when the tty_tickets option is enabled, does not properly validate the controlling terminal device, which allows local users with sudo permissions to hijack the authorization of another terminal via vectors related to a session without a controlling terminal device and connecting to the standard input, output, and error file descriptors of another terminal. NOTE: this is one of three closely-related vulnerabilities that were originally assigned CVE-2013-1776, but they have been SPLIT because of different affected versions.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is a local sudo authorization-boundary issue. On systems using affected sudo versions with tty_tickets enabled, a local user who already has sudo permissions could reuse another terminal’s sudo authorization. It is not described as remote code execution, and the provided sources do not show active exploitation. Exposure is most likely on legacy Unix-like systems running affected sudo versions with tty_tickets enabled. Business risk is higher on shared administrative servers, jump hosts, developer systems, or multi-user environments where multiple sudo-capable users have interactive shell access. Prioritize remediation where older sudo versions remain on shared systems. The issue is local and permission-dependent, so it is not an internet-facing emergency, but it can weaken administrative separation on sensitive hosts. Mitigation focus: Upgrade sudo to 1.7.10p5, 1.8.6p6, or vendor-fixed packages.; Review Debian, Red Hat, Slackware, Apple, and sudo project advisories for platform-specific fixes.; Confirm whether tty_tickets is enabled on managed Unix-like systems..

Prepared

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-2013-2777 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
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
5Source links

CVSS and timeline data

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

Source materials

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.