GHSA-g6pw-999w-j75m: Elf rs ELF Header Parsing Library Doesn't Vulnerability

MODERATE
Share
Published
Advisory Summary

GHSA-g6pw-999w-j75m is a MODERATE elf header parsing library doesn't vulnerability (General Security Weakness) affecting Elf rs libraries in the crates.io ecosystem. The issue involves elf header parsing library doesn't check for valid offset. Remediation is available by upgrading affected packages to version 0.3.0.

GHSA-g6pw-999w-j75m at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-g6pw-999w-j75m
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Elf rs
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix GHSA-g6pw-999w-j75m

To remediate this vulnerability, upgrade all affected Elf rs dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

elf_rs fixed: 0.3.0 
Upgrade elf_rs to 0.3.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for elf_rs

How to Check if You Are Affected

To determine whether your application is affected by GHSA-g6pw-999w-j75m, inspect your project dependencies for Elf rs:

inspect dependencies for elf_rs

Analyze the terminal output to locate any version of Elf rs in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.3.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Elf rs, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

The crate has several unsafe sections that don't perform proper pointer validation. An example can be found in the following function: ``` fn section_header_raw(&self) -> &[ET::SectionHeader] { let sh_off = self.elf_header().section_header_offset() as usize; let sh_num = self.elf_header().section_header_entry_num() as usize; unsafe { let sh_ptr = self.content().as_ptr().add(sh_off); from_raw_parts(sh_ptr as *const ET::SectionHeader, sh_num) } } ``` While this will work perfectly fine *if* the ELF header is valid, malicious or malformed input can contain a section header offset of an arbitrary size, meaning that the resultant pointer in the unsafe block can point to an artibrary address in the address space of the process. This can result in unpredictable behaviour, and in our fuzz testing, we discovered that it's trivial to cause SIGABRT (signal 6), or SEGV (signal 11). The function should either be marked as unsafe, with a note that the caller is responsible for providing only valid inputs, or it should ideally do the due diligence to ensure that the offset doesn't exceed the bounds of the header (and add additional checks as necessary).

GHSA-g6pw-999w-j75m Affected Elf rs Versions

1 component(s)
Fixed Versions:
0.3.0
Product / Package Ecosystem Affected Versions Fixed Version
elf_rs
 crates.io
< 0.3.0
0.3.0

References

Elf rs Source Repository REPOSITORY
https://github.com/vincenthouyi/elf_rs/issues/11
Elf rs Source Repository REPOSITORY
https://github.com/vincenthouyi/elf_rs
rustsec.org/advisories/rustsec-... WEB
https://rustsec.org/advisories/RUSTSEC-2022-0079.html

Frequently Asked Questions

What is GHSA-g6pw-999w-j75m?
GHSA-g6pw-999w-j75m is a security vulnerability in Elf rs involving ELF header parsing library doesn't check for valid offset under General Security Weakness.
Which Elf rs versions are affected?
Affected versions include releases prior to 0.3.0 across affected packages: elf_rs.
What version fixes GHSA-g6pw-999w-j75m?
Upgrading to 0.3.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is elf_rs affected?
Yes, elf_rs is affected in releases prior to 0.3.0. Upgrade your dependency to 0.3.0 or later.
What CWE is associated with GHSA-g6pw-999w-j75m?
GHSA-g6pw-999w-j75m is classified under General Security Weakness.
How can I check crates.io dependencies for GHSA-g6pw-999w-j75m?
Run the dependency tree command: 'inspect dependencies for elf_rs'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-g6pw-999w-j75m",
  "modified" : "2023-01-20T22:41:01Z",
  "published" : "2023-01-20T22:41:01Z",
  "aliases" : [ ],
  "summary" : "ELF header parsing library doesn't check for valid offset",
  "details" : "The crate has several unsafe sections that don't perform proper pointer validation.\n\nAn example can be found in the following function:\n\n```\nfn section_header_raw(&self) -> &[ET::SectionHeader] {\n    let sh_off = self.elf_header().section_header_offset() as usize;\n    let sh_num = self.elf_header().section_header_entry_num() as usize;\n    unsafe {\n        let sh_ptr = self.content().as_ptr().add(sh_off);\n        from_raw_parts(sh_ptr as *const ET::SectionHeader, sh_num)\n    }\n}\n```\n\nWhile this will work perfectly fine *if* the ELF header is valid, malicious or malformed input can contain a section header offset of an arbitrary size, meaning that the resultant pointer in the unsafe block can point to an artibrary address in the address space of the process.\n\nThis can result in unpredictable behaviour, and in our fuzz testing, we discovered that it's trivial to cause SIGABRT (signal 6), or SEGV (signal 11).\n\nThe function should either be marked as unsafe, with a note that the caller is responsible for providing only valid inputs, or it should ideally do the due diligence to ensure that the offset doesn't exceed the bounds of the header (and add additional checks as necessary).\n\n",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "elf_rs"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.3.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/vincenthouyi/elf_rs/issues/11"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/vincenthouyi/elf_rs"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2022-0079.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-01-20T22:41:01Z",
    "nvd_published_at" : null
  }
}