Subj : Re: Compiling from source
To   : Oli
From : Avon
Date : Wed Jan 27 2021 19:54:57

On 26 Jan 2021 at 10:32a, Oli pondered and said...
 
 Ol>  A> ! NNTP server did not accept message
 Ol>  A> free(): double free detected in tcache 2
 Ol>   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Ol>  A> Aborted
 Ol> 
 Ol>  A> Despite the failed post Spoon is not exiting correctly. This has been 
 Ol>  A> same error I have seen in all my test compiles.
 Ol> 
 Ol> I think we need help from a Professional

A Google search revealed this info.

https://bit.ly/2YjfS5m

trying to assign l from an uninitialised array str

...and this link seemed helpful.

https://bit.ly/3cc3Ene

[snip]

Double free errors occur when free() is called more than once with the same
memory address as an argument.

Calling free() twice on the same value can lead to memory leak. When a
program calls free() twice with the same argument, the program's memory
management data structures become corrupted and could allow a malicious user
to write values in arbitrary memory spaces. This corruption can cause the
program to crash or, in some circumstances, alter the execution flow. By
overwriting particular registers or memory spaces, an attacker can trick the
program into executing code of their own choosing, often resulting in an
interactive shell with elevated permissions.

When a buffer is free()'d, a linked list of free buffers is read to rearrange
and combine the chunks of free memory (to be able to allocate larger buffers
in the future). These chunks are laid out in a double linked list which
points to previous and next chunks. Unlinking an unused buffer (which is what
happens when free() is called) could allow an attacker to write arbitrary
values in memory; essentially overwriting valuable registers, calling
shellcode from its own buffer.

[snip]

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

.