CAPEC Definitions

    CAPEC Definitions / CAPEC-691

    CAPEC-691: Spoof Open-Source Software Metadata

    An adversary spoofs open-source software metadata in an attempt to masquerade malicious software as popular, maintained, and trusted.

    Severity:High
    Possibility:Medium

    Extended Description

    Due to open-source software's popularity, it serves as a desirable attack-vector for adversaries since a single malicious component may result in the exploitation of numerous systems/applications. Adversaries may, therefore, spoof the metadata pertaining to the open-source software in order to trick victims into downloading and using their malicious software. Examples of metadata that may be spoofed include: Owner of the software (e.g., repository or package owner) Author(s) of repository commits Frequency of repository commits Date/Time of repository commits Package or Repository "stars" Once the malicious software component has been integrated into an underlying application or executed on a system, the adversary is ultimately able to achieve numerous negative technical impacts within the system/application. This often occurs without any indication of compromise.

    Mitigations

    Before downloading open-source software, perform precursory metadata checks to determine the author(s), frequency of updates, when the software was last updated, and if the software is widely leveraged.

    Within package managers, look for conflicting or non-unique repository references to determine if multiple packages share the same repository reference.

    Reference vulnerability databases to determine if the software contains known vulnerabilities.

    Only download open-source software from reputable hosting sites or package managers.

    Only download open-source software that has been adequately signed by the developer(s). For repository commits/tags, look for the Verified status and for developers leveraging Vigilant Mode (GitHub) or similar modes.

    After downloading open-source software, ensure integrity values have not changed.

    Before executing or incorporating the software, leverage automated testing techniques (e.g., static and dynamic analysis) to determine if the software behaves maliciously.

    Relationships with other CAPECs

    CAPEC-690: Metadata Spoofing

    CAPEC-184: Software Integrity Attack

    CAPEC-444: Development Alteration

    CAPEC-630: TypoSquatting

    Prerequisites

    Identification of a popular open-source component whose metadata is to be spoofed.

    Related Weaknesses

    CWE-494: Download of Code Without Integrity Check