BundleTarget

Remarks

The first file a shipped game opens and the first one a content update downloads. A bundle's header names an entry count, each entry names an offset and a length, and all three are 32-bit unsigned numbers that decide where a slice lands — so this is the same shape as a packet's length prefix, with a file behind it instead of a datagram.

⚠ Opened with the checksum on. The CRC is optional by design — verifying two hundred megabytes on every open defeats the point of a lazily-read file — but the path that does verify is the one that runs on content off a network, which is the untrusted one. Leaving it off here would fuzz the trusted half.

Every id is enumerated and every one is read, because the index and the payload fail differently: an entry can be sorted wrongly, which the enumeration cannot see and the lookup answers "not found" to, and it can point past the end, which only the read finds.

Fields and properties (2)

• public string Name

  What to call it on a command line and in a report.

• public string What

  Which receive path this is, in one line.

Methods (3)

• public long AllowanceFor(int inputLength)

  How many bytes an input may cause to be allocated.

• public void Seed(ICollection<byte[]> corpus)

  Adds well-formed inputs for the mutator to start from.

• public long Run(ReadOnlySpan<byte> input)

  Pushes one input through the decoder.

Used by (1)

• FuzzTargetsVixen.Fuzz