TrevorC2 v1.1/v1.2 fails to prevent fingerprinting primarily via a discrepancy between response headers when responding to different HTTP methods, also via predictible responses when accessing and interacting with the "SITEPATHQUERY".
{
"source": "CPE_STRING",
"cpe": [
"cpe:2.3:a:trustedsec:trevorc2:1.1:*:*:*:*:*:*:*",
"cpe:2.3:a:trustedsec:trevorc2:1.2:*:*:*:*:*:*:*"
],
"extracted_events": [
{
"introduced": "1.1"
},
{
"last_affected": "1.1"
},
{
"introduced": "1.2"
},
{
"last_affected": "1.2"
}
]
}