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 "SITE_PATH_QUERY".
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not.
Link | Tags |
---|---|
https://github.com/trustedsec/trevorc2/blob/master/CHANGELOG.txt | third party advisory |
https://github.com/trustedsec/trevorc2/issues/18 | issue tracking third party advisory |