libmagic-rs 0.12.5

// Copyright (c) 2025-2026 the libmagic-rs contributors
// SPDX-License-Identifier: Apache-2.0

//! Offset resolution for magic rule evaluation
//!
//! This module provides functions for resolving different types of offset specifications
//! into absolute byte positions within file buffers, with proper bounds checking.

mod absolute;
mod indirect;
mod relative;

pub use absolute::{OffsetError, resolve_absolute_offset};

use crate::LibmagicError;
use crate::parser::ast::OffsetSpec;

/// Map an `OffsetError` to a `LibmagicError` for a given original offset value
pub(crate) fn map_offset_error(e: &OffsetError, original_offset: i64) -> LibmagicError {
    match e {
        OffsetError::BufferOverrun {
            offset,
            buffer_len: _,
        } => LibmagicError::EvaluationError(crate::error::EvaluationError::BufferOverrun {
            offset: *offset,
        }),
        OffsetError::InvalidOffset { reason: _ } | OffsetError::ArithmeticOverflow => {
            LibmagicError::EvaluationError(crate::error::EvaluationError::InvalidOffset {
                offset: original_offset,
            })
        }
    }
}

/// Resolve any offset specification to an absolute position.
///
/// Convenience wrapper for callers that do not have a relative-offset anchor
/// (e.g., tests, top-level evaluation with no prior match). Internally
/// delegates with `last_match_end = 0`. For `OffsetSpec::Relative`, that
/// means non-negative deltas behave like absolute offsets from the start of
/// the buffer (`Relative(N)` for `N >= 0` resolves to absolute `N`), but
/// negative deltas underflow the anchor and return
/// `EvaluationError::InvalidOffset` -- they are *not* interpreted like
/// `OffsetSpec::Absolute(-N)` from the end of the buffer. Callers that need
/// relative offsets to anchor against actual prior matches should use
/// `evaluate_rules` and let the engine thread the anchor.
///
/// **Behavior change:** before the relative-offset feature landed in v0.5,
/// this function returned `EvaluationError::UnsupportedType` for
/// `OffsetSpec::Relative`. It now resolves against anchor 0, which can
/// succeed (non-negative delta) or fail with `InvalidOffset` (negative
/// delta) depending on the value. Callers with existing error-handling code
/// that pattern-matched `UnsupportedType` for relative offsets must remove
/// that arm.
///
/// # Arguments
///
/// * `spec` - The offset specification to resolve
/// * `buffer` - The file buffer to resolve against
///
/// # Returns
///
/// Returns the resolved absolute offset as a `usize`, or a `LibmagicError` if resolution fails.
///
/// # Examples
///
/// ```rust
/// use libmagic_rs::evaluator::offset::resolve_offset;
/// use libmagic_rs::parser::ast::OffsetSpec;
///
/// let buffer = b"Test data";
/// let spec = OffsetSpec::Absolute(4);
///
/// let offset = resolve_offset(&spec, buffer).unwrap();
/// assert_eq!(offset, 4);
/// ```
///
/// # Errors
///
/// * `LibmagicError::EvaluationError` - If offset resolution fails
pub fn resolve_offset(spec: &OffsetSpec, buffer: &[u8]) -> Result<usize, LibmagicError> {
    resolve_offset_with_context(spec, buffer, 0)
}

/// Resolve any offset specification, including relative offsets, against a
/// previous-match anchor.
///
/// This is the full dispatcher used by the evaluation engine. It handles all
/// `OffsetSpec` variants:
///
/// - [`OffsetSpec::Absolute`] / [`OffsetSpec::FromEnd`]: resolved against the
///   buffer (sign-aware), `last_match_end` ignored.
/// - [`OffsetSpec::Indirect`]: resolved by reading a pointer value from the
///   buffer, `last_match_end` ignored.
/// - [`OffsetSpec::Relative`]: resolved as `last_match_end + delta`,
///   bounds-checked. The anchor `0` makes top-level relative offsets resolve
///   from the file start.
///
/// `pub(crate)` because the anchor-threading contract is internal to the
/// evaluation engine -- external callers use [`resolve_offset`] (which
/// hardcodes anchor 0) or go through `evaluate_rules`.
///
/// # Arguments
///
/// * `spec` - The offset specification to resolve
/// * `buffer` - The file buffer to resolve against
/// * `last_match_end` - End offset of the most recent successful match.
///   Supplied by the engine via `EvaluationContext::last_match_end()`. Pass
///   `0` if no prior match exists.
///
/// # Errors
///
/// * `LibmagicError::EvaluationError` - If offset resolution fails for any
///   variant. Relative-offset failures surface as `BufferOverrun` (target
///   past end of buffer) or `InvalidOffset` (arithmetic over/underflow).
pub(crate) fn resolve_offset_with_context(
    spec: &OffsetSpec,
    buffer: &[u8],
    last_match_end: usize,
) -> Result<usize, LibmagicError> {
    resolve_offset_with_base(spec, buffer, last_match_end, 0)
}

/// Like [`resolve_offset_with_context`] but applies a subroutine
/// `base_offset` to positive absolute offsets.
///
/// Inside a `MetaType::Use` subroutine body, `OffsetSpec::Absolute(n)`
/// with `n >= 0` resolves to `base_offset + n`, matching magic(5)
/// semantics where the subroutine's offsets are relative to the
/// caller's invocation point. `Indirect` takes the base on its
/// pointer-read SITE only -- the value read through the pointer stays
/// an absolute file position (GOTCHAS S3.10). Negative `Absolute`,
/// `FromEnd`, and `Relative` are unaffected -- they already have
/// well-defined frames of reference (buffer end or previous match).
pub(crate) fn resolve_offset_with_base(
    spec: &OffsetSpec,
    buffer: &[u8],
    last_match_end: usize,
    base_offset: usize,
) -> Result<usize, LibmagicError> {
    match spec {
        OffsetSpec::Absolute(offset) => {
            // Apply base_offset only to positive absolute offsets.
            // Negative values mean "from end" and should not be shifted
            // by the subroutine base.
            let effective = if *offset >= 0 {
                // Use checked conversions so overflow is reported as
                // InvalidOffset rather than silently producing a huge
                // biased value that later surfaces as BufferOverrun.
                let abs = usize::try_from(*offset).map_err(|_| {
                    LibmagicError::EvaluationError(crate::error::EvaluationError::InvalidOffset {
                        offset: *offset,
                    })
                })?;
                let biased = base_offset
                    .checked_add(abs)
                    .ok_or(LibmagicError::EvaluationError(
                        crate::error::EvaluationError::InvalidOffset { offset: *offset },
                    ))?;
                i64::try_from(biased).map_err(|_| {
                    LibmagicError::EvaluationError(crate::error::EvaluationError::InvalidOffset {
                        offset: *offset,
                    })
                })?
            } else {
                *offset
            };
            resolve_absolute_offset(effective, buffer).map_err(|e| map_offset_error(&e, effective))
        }
        OffsetSpec::Indirect { .. } => indirect::resolve_indirect_offset_with_anchor(
            spec,
            buffer,
            Some(last_match_end),
            base_offset,
        ),
        OffsetSpec::Relative(_) => relative::resolve_relative_offset(spec, buffer, last_match_end),
        OffsetSpec::FromEnd(offset) => {
            // `FromEnd(0)` is the magic(5) `-0` form: the end-of-file
            // *position* (`buffer.len()`), one past the last readable byte.
            // It is valid as a position value for the `offset` pseudo-type
            // (which never reads there) even though `resolve_absolute_offset`
            // would wrongly send `0` through its positive path and resolve to
            // start-of-file. Negative `FromEnd` deltas keep the shared
            // from-end resolution (identical to negative `Absolute`); base
            // offset never applies -- "from end" is always relative to the
            // buffer itself.
            if *offset == 0 {
                return Ok(buffer.len());
            }
            resolve_absolute_offset(*offset, buffer).map_err(|e| map_offset_error(&e, *offset))
        }
    }
}

#[cfg(test)]
mod tests {
    use super::*;

    #[test]
    fn test_resolve_offset_absolute() {
        let buffer = b"Test data for offset resolution";
        let spec = OffsetSpec::Absolute(5);

        let result = resolve_offset(&spec, buffer).unwrap();
        assert_eq!(result, 5);
    }

    #[test]
    fn test_resolve_offset_absolute_negative() {
        let buffer = b"Test data";
        let spec = OffsetSpec::Absolute(-4);

        let result = resolve_offset(&spec, buffer).unwrap();
        assert_eq!(result, 5); // 9 - 4 = 5
    }

    #[test]
    fn test_resolve_offset_from_end() {
        let buffer = b"Test data";
        let spec = OffsetSpec::FromEnd(-3);

        let result = resolve_offset(&spec, buffer).unwrap();
        assert_eq!(result, 6); // 9 - 3 = 6
    }

    #[test]
    fn test_resolve_offset_absolute_out_of_bounds() {
        let buffer = b"Short";
        let spec = OffsetSpec::Absolute(10);

        let result = resolve_offset(&spec, buffer);
        assert!(result.is_err());

        match result.unwrap_err() {
            LibmagicError::EvaluationError(crate::error::EvaluationError::BufferOverrun {
                ..
            }) => {
                // Expected error type
            }
            _ => panic!("Expected EvaluationError with BufferOverrun"),
        }
    }

    #[test]
    fn test_resolve_offset_indirect_success() {
        // Byte pointer at offset 0 with value 5 → resolves to offset 5
        let buffer = b"\x05TestXdata";
        let spec = OffsetSpec::Indirect {
            base_offset: 0,
            base_relative: false,
            pointer_type: crate::parser::ast::TypeKind::Byte { signed: false },
            adjustment: 0,
            adjustment_op: crate::parser::ast::IndirectAdjustmentOp::Add,
            result_relative: false,
            endian: crate::parser::ast::Endianness::Little,
        };

        let result = resolve_offset(&spec, buffer).unwrap();
        assert_eq!(result, 5);
    }

    #[test]
    fn test_resolve_offset_relative_via_context() {
        // Anchor 4 + delta 3 = absolute 7, in-bounds.
        let buffer = b"0123456789ABCDEF";
        let spec = OffsetSpec::Relative(3);
        let resolved = resolve_offset_with_context(&spec, buffer, 4).unwrap();
        assert_eq!(resolved, 7);
    }

    #[test]
    fn test_resolve_offset_relative_top_level_default() {
        // Calling resolve_offset (no context) should default the anchor to 0.
        let buffer = b"0123456789ABCDEF";
        let spec = OffsetSpec::Relative(5);
        assert_eq!(resolve_offset(&spec, buffer).unwrap(), 5);
    }

    #[test]
    fn test_resolve_offset_with_context_passthrough_absolute() {
        // The context-aware dispatcher must not affect non-relative variants.
        let buffer = b"Test data";
        let spec = OffsetSpec::Absolute(4);
        // last_match_end is irrelevant for Absolute.
        assert_eq!(resolve_offset_with_context(&spec, buffer, 100).unwrap(), 4);
    }

    #[test]
    fn test_resolve_offset_with_context_passthrough_from_end() {
        let buffer = b"Test data";
        let spec = OffsetSpec::FromEnd(-3);
        assert_eq!(resolve_offset_with_context(&spec, buffer, 999).unwrap(), 6);
    }

    #[test]
    fn test_resolve_from_end_zero_is_eof_position() {
        // The magic(5) `-0` form (`FromEnd(0)`) resolves to the end-of-file
        // POSITION -- `buffer.len()`, one past the last byte -- NOT offset 0.
        // `resolve_absolute_offset(0)` would wrongly send it through the
        // positive path and yield 0/start; the FromEnd arm special-cases it.
        // Used by gzip's `>>-0 offset >48` trailing-size gate.
        let buffer = b"Test data"; // 9 bytes
        assert_eq!(
            resolve_offset_with_context(&OffsetSpec::FromEnd(0), buffer, 0).unwrap(),
            buffer.len(),
            "FromEnd(0) must resolve to the EOF position (buffer.len())"
        );
        // Distinct from a real absolute 0.
        assert_eq!(
            resolve_offset_with_context(&OffsetSpec::Absolute(0), buffer, 0).unwrap(),
            0
        );
        // Empty buffer: EOF position is 0, and that must not error.
        assert_eq!(
            resolve_offset_with_context(&OffsetSpec::FromEnd(0), b"", 0).unwrap(),
            0
        );
    }

    #[test]
    fn test_resolve_offset_with_context_passthrough_indirect() {
        // Same indirect setup as test_resolve_offset_indirect_success above.
        let buffer = b"\x05TestXdata";
        let spec = OffsetSpec::Indirect {
            base_offset: 0,
            base_relative: false,
            pointer_type: crate::parser::ast::TypeKind::Byte { signed: false },
            adjustment: 0,
            adjustment_op: crate::parser::ast::IndirectAdjustmentOp::Add,
            result_relative: false,
            endian: crate::parser::ast::Endianness::Little,
        };
        assert_eq!(resolve_offset_with_context(&spec, buffer, 42).unwrap(), 5);
    }

    #[test]
    fn test_resolve_offset_with_base_biases_positive_absolute() {
        // Positive Absolute inside a subroutine body is biased by
        // `base_offset`. This is the load-bearing invariant of
        // `MetaType::Use` subroutine semantics.
        let buffer = b"0123456789ABCDEF";
        let spec = OffsetSpec::Absolute(4);
        // base_offset = 10 -> resolves to 14 (not 4).
        assert_eq!(
            resolve_offset_with_base(&spec, buffer, 0, 10).unwrap(),
            14,
            "positive Absolute must be biased by base_offset inside a subroutine"
        );
    }

    #[test]
    fn test_resolve_offset_with_base_does_not_bias_negative_absolute() {
        // Negative Absolute means "from-end" semantics (magic(5)
        // allows either explicit `FromEnd` or negative `Absolute`).
        // The subroutine base_offset is relative to the file start
        // and has no meaning for from-end positions.
        let buffer = b"0123456789ABCDEF";
        let spec = OffsetSpec::Absolute(-4);
        // Without bias: resolves to len - 4 = 12.
        // Buggy with-bias would give: 10 + (len - 4) or similar.
        assert_eq!(
            resolve_offset_with_base(&spec, buffer, 0, 10).unwrap(),
            12,
            "negative Absolute must NOT be biased"
        );
    }

    #[test]
    fn test_resolve_offset_with_base_does_not_bias_from_end() {
        // `FromEnd` is always relative to the buffer, not the
        // subroutine's use-site.
        let buffer = b"0123456789ABCDEF";
        let spec = OffsetSpec::FromEnd(-4);
        assert_eq!(
            resolve_offset_with_base(&spec, buffer, 0, 10).unwrap(),
            12,
            "FromEnd must NOT be biased"
        );
    }

    #[test]
    fn test_resolve_offset_with_base_does_not_bias_relative() {
        // `Relative(N)` resolves against the previous-match anchor,
        // not the subroutine base. Inside a subroutine body,
        // `last_match_end` is seeded to the use-site by
        // `SubroutineScope::enter`, so this already has the correct
        // frame of reference without additional bias.
        let buffer = b"0123456789ABCDEF";
        let spec = OffsetSpec::Relative(3);
        // last_match_end = 2, base_offset = 10.
        // Expected: 2 + 3 = 5 (bias does NOT apply).
        assert_eq!(
            resolve_offset_with_base(&spec, buffer, 2, 10).unwrap(),
            5,
            "Relative must NOT be biased (already resolved against last_match_end)"
        );
    }

    /// Build a byte-pointer `Indirect` spec for the base-bias tests.
    fn byte_pointer_spec(base_offset: i64, base_relative: bool) -> OffsetSpec {
        OffsetSpec::Indirect {
            base_offset,
            base_relative,
            pointer_type: crate::parser::ast::TypeKind::Byte { signed: false },
            adjustment: 0,
            adjustment_op: crate::parser::ast::IndirectAdjustmentOp::Add,
            result_relative: false,
            endian: crate::parser::ast::Endianness::Little,
        }
    }

    /// The pointer-read SITE takes the subroutine base bias.
    ///
    /// This is the `mach-o` case: `use mach-o` at file offset 8 makes
    /// `>(8.L)` read at `8 + 8 = 16` (`arch[0].offset`), not at 8
    /// (`arch[0].cputype`). Splitting the read site from the dereferenced
    /// result is what makes GOTCHAS S3.10's subroutine semantics hold for
    /// indirect offsets.
    #[test]
    fn test_resolve_offset_with_base_biases_indirect_pointer_read_site() {
        // Decoy pointer 3 at offset 0; real pointer 5 at offset 10.
        let buffer = b"\x03\x00\x00\x00\x00\x00\x00\x00\x00\x00\x05data";
        let spec = byte_pointer_spec(0, false);

        // base_offset 10 -> read the pointer at 10 (value 5), not at 0 (value 3).
        assert_eq!(
            resolve_offset_with_base(&spec, buffer, 0, 10).unwrap(),
            5,
            "the pointer-read site must be biased by the subroutine base"
        );

        // With no subroutine base the read site is unchanged (top-level behavior).
        assert_eq!(
            resolve_offset_with_base(&spec, buffer, 0, 0).unwrap(),
            3,
            "base 0 must leave the pointer-read site untouched"
        );
    }

    /// The dereferenced RESULT never takes the bias.
    ///
    /// The value read through the pointer is an absolute file position.
    /// Biasing it too would break every `use` subroutine whose pointer
    /// holds an absolute offset.
    #[test]
    fn test_resolve_offset_with_base_does_not_bias_indirect_result() {
        let buffer = b"\x03\x00\x00\x00\x00\x00\x00\x00\x00\x00\x05data";
        let spec = byte_pointer_spec(0, false);

        let resolved = resolve_offset_with_base(&spec, buffer, 0, 10).unwrap();
        assert_eq!(
            resolved, 5,
            "the pointer value is an absolute position and must not be biased"
        );
        assert_ne!(
            resolved, 15,
            "a biased result (base 10 + value 5) is the failure this pins"
        );
    }

    /// `(&N.X)` is not double-biased.
    ///
    /// `base_relative` already resolves against the anchor, and
    /// `SubroutineScope::enter` seeds anchor and base to the same use-site
    /// value, so applying the base here as well would count it twice.
    ///
    /// Unlike its two siblings above, this passes against the pre-fix
    /// implementation too -- the `base_relative` arm was never biased. It is
    /// a forward-looking guard against someone extending the bias to that
    /// arm, not regression coverage for #378.
    #[test]
    fn test_resolve_offset_with_base_does_not_double_bias_base_relative_indirect() {
        // Pointer 7 at offset 8; a decoy 9 at offset 16 catches double-biasing.
        let buffer =
            b"\x00\x00\x00\x00\x00\x00\x00\x00\x07\x00\x00\x00\x00\x00\x00\x00\x09\x00\x00\x00";
        let spec = byte_pointer_spec(0, true);

        // anchor 8, base 8 -> read at anchor + 0 = 8 (value 7), never at 16.
        assert_eq!(
            resolve_offset_with_base(&spec, buffer, 8, 8).unwrap(),
            7,
            "base_relative resolves against the anchor only; the base must not be added again"
        );
    }

    /// The subroutine-base bias reports overflow as `InvalidOffset`.
    ///
    /// The sibling overflow test above covers the `Absolute` arm; this covers
    /// `offset_plus_base` on the `Indirect` pointer-read site, which has its
    /// own conversion and checked add.
    #[test]
    fn test_resolve_offset_with_base_indirect_overflow_yields_invalid_offset() {
        let buffer = b"\x03\x00\x00\x00\x00\x00\x00\x00\x00\x00\x05data";
        let cases: &[(i64, usize)] = &[
            // base converts cleanly, then base + site overflows the checked add
            (i64::MAX, usize::MAX >> 1),
            // base cannot convert to i64 at all
            (2, usize::MAX),
        ];
        for &(base_offset, subroutine_base) in cases {
            let spec = byte_pointer_spec(base_offset, false);
            let result = resolve_offset_with_base(&spec, buffer, 0, subroutine_base);
            match result {
                Err(LibmagicError::EvaluationError(
                    crate::error::EvaluationError::InvalidOffset { .. },
                )) => {}
                other => panic!(
                    "base {subroutine_base} + site {base_offset} must be InvalidOffset, got {other:?}"
                ),
            }
        }
    }

    /// `(&N.X)` resolves against the anchor, never the subroutine base.
    ///
    /// The sibling test uses an equal anchor and base, so an implementation
    /// that read the base would still pass it. Here they differ, so only
    /// reading `last_match_end` produces the expected result.
    #[test]
    fn test_base_relative_indirect_reads_anchor_not_base() {
        // Pointer 7 at offset 8 (the anchor); decoy 9 at offset 16 (the base).
        let buffer =
            b"\x00\x00\x00\x00\x00\x00\x00\x00\x07\x00\x00\x00\x00\x00\x00\x00\x09\x00\x00\x00";
        let spec = byte_pointer_spec(0, true);

        // anchor 8, base 16 -> read at the anchor (value 7), not the base (9).
        assert_eq!(
            resolve_offset_with_base(&spec, buffer, 8, 16).unwrap(),
            7,
            "base_relative must resolve against last_match_end, not base_offset"
        );
        // Swapping them proves the test discriminates rather than passing by luck.
        assert_eq!(
            resolve_offset_with_base(&spec, buffer, 16, 8).unwrap(),
            9,
            "moving the anchor must move the pointer-read site"
        );
    }

    #[test]
    fn test_resolve_offset_comprehensive() {
        let buffer = b"0123456789ABCDEF";

        // Test various absolute offsets
        let test_cases = vec![
            (OffsetSpec::Absolute(0), 0),
            (OffsetSpec::Absolute(8), 8),
            (OffsetSpec::Absolute(15), 15),
            (OffsetSpec::Absolute(-1), 15),
            (OffsetSpec::Absolute(-8), 8),
            (OffsetSpec::Absolute(-16), 0),
            (OffsetSpec::FromEnd(-1), 15),
            (OffsetSpec::FromEnd(-8), 8),
            (OffsetSpec::FromEnd(-16), 0),
        ];

        for (spec, expected) in test_cases {
            let result = resolve_offset(&spec, buffer).unwrap();
            assert_eq!(result, expected, "Failed for spec: {spec:?}");
        }
    }

    /// Regression test for RU0: `base_offset + large_positive_absolute` that
    /// overflows `usize` must produce `InvalidOffset`, not `BufferOverrun`.
    ///
    /// Before the fix, saturating arithmetic turned overflow into `usize::MAX`
    /// (or `i64::MAX`), which then flowed into `resolve_absolute_offset` and
    /// surfaced as a `BufferOverrun` at that giant offset -- losing the more
    /// precise overflow signal.
    #[test]
    fn test_resolve_offset_with_base_overflow_yields_invalid_offset() {
        let buffer = b"0123456789ABCDEF"; // 16 bytes
        // base_offset near usize::MAX combined with any positive Absolute
        // must overflow. Use usize::MAX - 1 so that adding even 2 overflows.
        let base = usize::MAX - 1;
        let spec = OffsetSpec::Absolute(2); // base + 2 overflows usize

        let result = resolve_offset_with_base(&spec, buffer, 0, base);
        assert!(
            result.is_err(),
            "overflow of base_offset + absolute must fail"
        );
        match result.unwrap_err() {
            LibmagicError::EvaluationError(crate::error::EvaluationError::InvalidOffset {
                ..
            }) => {
                // Correct: overflow reported as InvalidOffset, not BufferOverrun.
            }
            LibmagicError::EvaluationError(crate::error::EvaluationError::BufferOverrun {
                ..
            }) => {
                panic!(
                    "overflow of base_offset + absolute must be InvalidOffset, not BufferOverrun"
                );
            }
            other => panic!("unexpected error variant: {other:?}"),
        }
    }
}