docstring. Fingerprint creation A fingerprint is based on features extracted from a request. Usage of particular features from the full list (https://github.com/CERT-Polska/docs/feature_description.md) depends on the chosen report mode from a predefined list (more information on report modes is here (https://github.com/CERT-Polska/hfinger#report-modes)). The figure below represents the creation of an exemplary fingerprint in the default report mode.

Three parts of the request are analyzed to extract information: URI, headers' structure (including method and protocol version), and payload. Particular features of the fingerprint are separated using | (pipe). The final fingerprint generated for the POST request from the example is: 2|3|1|php|0.6|PO|1|us-ag,ac,ac-en,ho,co,co-ty,co-le|us-ag:f452d7a9/ac:as-as/ac-en:id/co:Ke-Al/co-ty:te-pl|A|4|1.4 The creation of features is described below in the order of appearance in the fingerprint. Firstly, URI features are extracted: * URI length represented as a logarithm base 10 of the length, rounded to an integer, (in the example URI is 43 characters long, so log10(43)≈2), * number of directories, (in the example there are 3 directories), * average directory length, represented as a logarithm with base 10 of the actual average length of the directory, rounded to an integer, (in the example there are three directories with total length of 20 characters (6+6+8), so log10(20/3)≈1), * extension of the requested file, but only if it is on a list of known extensions in hfinger/configs/extensions.txt, * average value length represented as a logarithm with base 10 of the actual average value length, rounded to one decimal point, (in the example two values have the same length of 4 characters, what is obviously equal to 4 characters, and log10(4)≈0.6). Secondly, header structure features are analyzed: * request method encoded as first two letters of the method (PO), * protocol version encoded as an integer (1 for version 1.1, 0 for version 1.0, and 9 for version 0.9), * order of the headers, * and popular headers and their values. To represent order of the headers in the request, each header's name is encoded according to the schema in hfinger/configs/headerslow.json, for example, User-Agent header is encoded as us-ag. Encoded names are separated by ,. If the header name does not start with an upper case letter (or any of its parts when analyzing compound headers such as Accept-Encoding), then encoded representation is prefixed with !. If the header name is not on the list of the known headers, it is hashed using FNV1a hash (https://en.wikipedia.org/wiki/Fowler%E2%80%93Noll%E2%80%93Vo_hash_function), and the hash is used as encoding. When analyzing popular headers, the request is checked if they appear in it. These headers are: * Connection * Accept-Encoding * Content-Encoding * Cache-Control * TE * Accept-Charset * Content-Type * Accept * Accept-Language * User-Agent When the header is found in the request, its value is checked against a table of typical values to create pairs of header_name_representation:value_representation. The name of the header is encoded according to the schema in hfinger/configs/headerslow.json (as presented before), and the value is encoded according to schema stored in hfinger/configs directory or configs.py file, depending on the header. In the above example Accept is encoded as ac and its value */* as as-as (asterisk-asterisk), giving ac:as-as. The pairs are inserted into fingerprint in order of appearance in the request and are delimited using /. If the header value cannot be found in the encoding table, it is hashed using the FNV1a hash.
If the header value is composed of multiple values, they are tokenized to provide a list of values delimited with ,, for example, Accept: */*, text/* would give ac:as-as,te-as. However, at this point of development, if the header value contains a "quality value" tag (q=), then the whole value is encoded with its FNV1a hash. Finally, values of User-Agent and Accept-Language headers are directly encoded using their FNV1a hashes. Finally, in the payload features: * presence of non-ASCII characters, represented with the letter N, and with A otherwise, * payload's Shannon entropy, rounded to an integer, * and payload length, represented as a logarithm with base 10 of the actual payload length, rounded to one decimal point. Report modes

Hfinger operates in five report modes, which differ in features represented in the fingerprint, thus information extracted from requests. These are (with the number used in the tool configuration): * mode 0 - producing a similar number of collisions and fingerprints as mode 2, but using fewer features, * mode 1 - representing all designed features, but producing a little more collisions than modes 0, 2, and 4, * mode 2 - optimal (the default mode), representing all features which are usually used during requests' analysis, but also offering a low number of collisions and generated fingerprints, * mode 3 - producing the lowest number of generated fingerprints from all modes, but achieving the highest number of collisions, * mode 4 - offering the highest fingerprint entropy, but also generating slightly more fingerprints than modes 0-2. The modes were chosen in order to optimize Hfinger's capabilities to uniquely identify malware families versus the number of generated fingerprints. Modes 0, 2, and 4 offer a similar number of collisions between malware families, however, mode 4 generates a little more fingerprints than the other two. Mode 2 represents more request features than mode 0 with a comparable number of generated fingerprints and collisions. Mode 1 is the only one representing all designed features, but it increases the number of collisions by almost two times comparing to modes 0, 1, and 4. Mode 3 produces at least two times fewer fingerprints than other modes, but it introduces about nine times more collisions. Description of all designed features is here (https://github.com/CERT-Polska/docs/feature_description.md). The modes consist of features (in the order of appearance in the fingerprint): * mode 0: * number of directories, * average directory length represented as an integer, * extension of the requested file, * average value length represented as a float, * order of headers, * popular headers and their values, * payload length represented as a float. * mode 1: * URI length represented as an integer, * number of directories, * average directory length represented as an integer, * extension of the requested file, * variable length represented as an integer, * number of variables, * average value length represented as an integer, * request method, * version of protocol, * order of headers, * popular headers and their values, * presence of non-ASCII characters, * payload entropy represented as an integer, * payload length represented as an integer. * mode 2: * URI length represented as an integer, * number of directories, * average directory length represented as an integer, * extension of the requested file, * average value length represented as a float, * request method, * version of protocol, * order of headers, * popular headers and their values, * presence of non-ASCII characters, * payload entropy represented as an integer, * payload length represented as a float. * mode 3: * URI length represented as an integer, * average directory length represented as an integer, * extension of the requested file, * average value length represented as an integer, * order of headers. * mode 4: * URI length represented as a float, * number of directories, * average directory length represented as a float, * extension of the requested file, * variable length represented as a float, * average value length represented as a float, * request method, * version of protocol, * order of headers, * popular headers and their values, * presence of non-ASCII characters, * payload entropy represented as a float, * payload length represented as a float.

Download Hfinger (https://github.com/CERT-Polska/hfinger)

OAuth CSRF: Exploiting the Authorization Code Flow for Account Takeover
https://medium.com/@cyberpro151/oauth-csrf-exploiting-the-authorization-code-flow-for-account-takeover-f67cee914d39?source=rss------bug_bounty-5

Hello everyone! It’s cyberpro151 back with another writeup about an Account Takeover vulnerability that I found using CSRF vulnerability…Continue reading on Medium » (https://medium.com/@cyberpro151/oauth-csrf-exploiting-the-authorization-code-flow-for-account-takeover-f67cee914d39?source=rss------bug_bounty-5)

Cross Site Scripting (XSS) Walkthrough — VulnLab XSS by Yavuzlar

VulnLab Yavuzlar is a virtual laboratory platform designed for cybersecurity training and testing. It is a simulated environment where…Continue reading on Medium »
Read more...

Insecure Direct Object Reference (IDOR) Walkthrough — VulnLab by Yavuzlar

Insecure Direct Object Reference (IDOR) is a vulnerability where a user can access and manipulate resources directly via an identifier…Continue reading on Medium »
Read more...

security+ to pentesting
https://www.reddit.com/r/Pentesting/comments/1dndz4w/security_to_pentesting/

<!-- SC_OFF -->Hello guys, i'm currently studying to get the security+ cert and i'm interested in pentesting and red teaming, so after getting the cert should i start learning in THM paths than move to HTB academy or start right away in HTB academy cuz i'm confused between both and i know THM is beginner friendly, keep in mind that i'm in my final year of software engineering and i studied some topics about cyber security at university so i'm not a complete beginner.
what do you recommend me to do ? <!-- SC_ON --> submitted by /u/LanguageSome2394 (https://www.reddit.com/user/LanguageSome2394)
[link] (https://www.reddit.com/r/Pentesting/comments/1dndz4w/security_to_pentesting/) [comments] (https://www.reddit.com/r/Pentesting/comments/1dndz4w/security_to_pentesting/)

OTP Bypass through Session Manipulation

IntroductionContinue reading on Medium »
Read more...

Unrestricted File Upload Walkthrough — VulnLab by Yavuzlar

Unrestricted File Upload is a vulnerability where an application allows users to upload files without proper validation or security checks…Continue reading on Medium »
Read more...

AI’s Dirty Little Secret: The Minefield of Forbidden Knowledge
https://www.reddit.com/r/redteamsec/comments/1dnf9ng/ais_dirty_little_secret_the_minefield_of/

submitted by /u/superc0w (https://www.reddit.com/user/superc0w)
[link] (https://generativeai.pub/ais-dirty-little-secret-the-minefield-of-forbidden-knowledge-c9553f2c1bee?sk=d1f31c5b8c99688cfc9ef3a90e7f7266) [comments] (https://www.reddit.com/r/redteamsec/comments/1dnf9ng/ais_dirty_little_secret_the_minefield_of/)

Aranea Alpha - The Ultimate Hacking Device
https://www.reddit.com/r/redteamsec/comments/1dnfck2/aranea_alpha_the_ultimate_hacking_device/

submitted by /u/TransitionTemporary5 (https://www.reddit.com/user/TransitionTemporary5)
[link] (https://www.indiegogo.com/projects/aranea-alpha-the-ultimate-hacking-device/x/37916744#/) [comments] (https://www.reddit.com/r/redteamsec/comments/1dnfck2/aranea_alpha_the_ultimate_hacking_device/)

Tutorial Install Burpsuite Beginner

Burp Suite adalah salah satu alat penting dalam pengujian keamanan aplikasi web. Alat ini dapat membantu Anda mengidentifikasi dan…Continue reading on Medium »
Read more...

Poodle Haney Bug Bounty

Hello,Continue reading on Medium »
Read more...

Cross Site Scripting (XSS) Walkthrough — VulnLab XSS by Yavuzlar
https://medium.com/@muhammadriva/cross-site-scripting-xss-walkthrough-vulnlab-xss-by-yavuzlar-149d14ab2d6b?source=rss------bug_bounty-5

VulnLab Yavuzlar is a virtual laboratory platform designed for cybersecurity training and testing. It is a simulated environment where…Continue reading on Medium » (https://medium.com/@muhammadriva/cross-site-scripting-xss-walkthrough-vulnlab-xss-by-yavuzlar-149d14ab2d6b?source=rss------bug_bounty-5)

Bug Bounty Programs: How Outsourcing Can Help Your Project — Sinhala Translation

Integritee විසින් Bug Bounty වැඩසටහනක් ආරම්භ කරයි, සදාචාරාත්මක හැකර්වරුන් සහ අපගේ තාක්ෂණය ගැන උනන්දුවක් දක්වන සංවර්ධකයින් දිරිමත් කරමින්…Continue reading on Medium »
Read more...

Bug Bounty Programs: How Outsourcing Can Help Your Project — Sinhala Translation
https://medium.com/@integriteesrilanka/bug-bounty-programs-how-outsourcing-can-help-your-project-sinhala-translation-0a40a97e58c7?source=rss------bug_bounty-5