LiveActive security incident?Get immediate response
CVE Record

CVE-2005-4582: Electric Sheep 2.6.3 does not require authentication or integrity checks from the server to the client, whi...

Electric Sheep 2.6.3 does not require authentication or integrity checks from the server to the client, which allows remote attackers to download and display arbitrary MPEG movie files via (1) DNS spoofing, (2) a URL on the command line, or (3) a URL in the configuration file. NOTE: the same attack vectors apply to common web browsers that are able to communicate with untrusted web servers, and other problems related to DNS design issues. Therefore this may not be a specific vulnerability. However, a client would reasonably expect to receive content only from the server.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Electric Sheep 2.6.3 may trust movie content delivered from a server without proving the server is authentic or the file is intact. A user could see attacker-supplied MPEG content if name resolution or configured URLs point to an untrusted server. The record itself notes this may be a general trust issue, not a product-specific flaw. Exposure appears limited to environments still running Electric Sheep 2.6.3 or similar legacy clients that retrieve content from untrusted or user-controlled URLs. Modern enterprise exposure is likely uncommon, but should be verified through endpoint software inventory rather than assumed absent. Treat this as a low operational priority unless Electric Sheep is present. The business decision is mainly legacy software cleanup: identify, remove, or tightly constrain the application rather than launch a broad emergency response. Mitigation focus: Inventory endpoints for Electric Sheep 2.6.3 or unmanaged legacy installations.; Remove or retire Electric Sheep where it is not business-required.; Check vendor or maintainer guidance for fixed versions or replacement recommendations..

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-2005-4582 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
2Source 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.