CYBERGEZ (@Cybergez) header
CYBERGEZ (@Cybergez) profile picture

Aspiring Ethical Hacker | Network Security | PenTesting & Recon | Learning, Practicing, Sharing

Joined February 2026
CYBERGEZ retweeted
Packet vs Frame vs Segment: What's the difference? πŸ€” You’ll often hear these three terms when studying network traffic, especially in #Wireshark. They are related, but they don't mean the same thing. Think of them as layers of a package:
2
7
1
13
393
Packet vs Frame vs Segment: What's the difference? πŸ€” You’ll often hear these three terms when studying network traffic, especially in #Wireshark. They are related, but they don't mean the same thing. Think of them as layers of a package:
2
7
1
13
393
The Data (Payload) It's the actual information being carried. For example, when you visit a website, your browser might send an HTTP request. That request is application data carried inside a TCP segment, which is inside an IP packet, which is inside a frame. It's like opening a package and finding another package inside!
1
6
38
Putting Everything Together Here's the relationship: Frame β†’ Packet β†’ Segment β†’ Data Each layer adds its own information to help move data across a network. And this is one reason Wireshark is so interesting. You can capture traffic and expand these sections to see how the different layers are structured. Once you understand this, reading packets in #Wireshark becomes a lot less confusing.
1
7
42
CYBERGEZ retweeted
Day 137 of my #EthicalHacking journey 🐍 Yesterday, I spent some time exploring #Python, particularly a module called "zipfile", which allows me to work with ZIP archives programmatically. I explored how to create, open, extract and manage compressed files. Out of curiosity, I also decided to explore "send2trash". What caught my attention was that instead of permanently deleting files, it sends them to the system's recycle bin or trash, just like when you normally delete something through the GUI. Didn't cover much yesterday, but I still got to explore something new and understand how these modules work. Not every day has to be packed with new concepts. Some days are just about getting a little further than you were yesterday. πŸ˜„ The journey continues!
Day 136 of my #EthicalHacking journey Today, I dove deeper into Python and explored three libraries: - os: For interacting with the operating system, working with files, directories and paths. - shutil: For high-level file operations like copying, moving and deleting files. - shelve: For storing and retrieving Python objects using a file-based database. I also explored some of their functions, including "os.path.isfile()", "shelve.open()" and "shutil.move()". I'm considering building a project that brings everything together. Still putting the pieces together, but I think it'll be a fun one. πŸ˜„
8
2
22
1,321
CYBERGEZ retweeted
Honestly, one thing I still don't understand is the excitement around having a touchscreen laptop as someone going into cybersecurity. πŸ˜‚ I've come across people in the field who are genuinely happy they spent extra to get a touchscreen laptop. Meanwhile, I'm here wondering... what exactly are you touching? πŸ˜‚
Day 138 of my #EthicalHacking journey. 🐧 Yesterday, I dove deeper into #Wireshark, learning two different filtering syntaxes. 1. BPF (Berkeley Packet Filter) – Used in Capture Filters to determine what traffic Wireshark captures. Examples: - "tcp port 80" – Capture TCP traffic on port 80. - "icmp" – Capture ICMP traffic. - "udp port 53" – Capture UDP traffic on port 53. I also discovered that ICMP isn't just about ping! There are different message types, including type 17, 8, 3 and 0. πŸ˜… 2. Wireshark Display Filter Syntax – Used to filter traffic that has already been captured. Examples: - "dns" – Show DNS traffic. - "tcp" – Show TCP traffic. - "tcp.flags.syn == 1" – Show packets with the SYN flag set. - "frame.len > 1000" – Show packets larger than 1,000 bytes. I also explored Protocol, Application, Field Existence and Characteristics filters, which introduced me to something called BOOTP. Honestly, Field Existence and Characteristics filters gave me the hardest time. Still learning, still figuring things out. One packet at a time. πŸ˜„
3
6
2
14
503
I find it funny πŸ˜‚πŸ˜‚ They think they will use the touch screen while monitoring logsπŸ˜‚
Honestly, one thing I still don't understand is the excitement around having a touchscreen laptop as someone going into cybersecurity. πŸ˜‚ I've come across people in the field who are genuinely happy they spent extra to get a touchscreen laptop. Meanwhile, I'm here wondering... what exactly are you touching? πŸ˜‚
1
2
2
29
Honestly, one thing I still don't understand is the excitement around having a touchscreen laptop as someone going into cybersecurity. πŸ˜‚ I've come across people in the field who are genuinely happy they spent extra to get a touchscreen laptop. Meanwhile, I'm here wondering... what exactly are you touching? πŸ˜‚
Day 138 of my #EthicalHacking journey. 🐧 Yesterday, I dove deeper into #Wireshark, learning two different filtering syntaxes. 1. BPF (Berkeley Packet Filter) – Used in Capture Filters to determine what traffic Wireshark captures. Examples: - "tcp port 80" – Capture TCP traffic on port 80. - "icmp" – Capture ICMP traffic. - "udp port 53" – Capture UDP traffic on port 53. I also discovered that ICMP isn't just about ping! There are different message types, including type 17, 8, 3 and 0. πŸ˜… 2. Wireshark Display Filter Syntax – Used to filter traffic that has already been captured. Examples: - "dns" – Show DNS traffic. - "tcp" – Show TCP traffic. - "tcp.flags.syn == 1" – Show packets with the SYN flag set. - "frame.len > 1000" – Show packets larger than 1,000 bytes. I also explored Protocol, Application, Field Existence and Characteristics filters, which introduced me to something called BOOTP. Honestly, Field Existence and Characteristics filters gave me the hardest time. Still learning, still figuring things out. One packet at a time. πŸ˜„
3
6
2
14
503
CYBERGEZ retweeted
Day 138 of my #EthicalHacking journey. 🐧 Yesterday, I dove deeper into #Wireshark, learning two different filtering syntaxes. 1. BPF (Berkeley Packet Filter) – Used in Capture Filters to determine what traffic Wireshark captures. Examples: - "tcp port 80" – Capture TCP traffic on port 80. - "icmp" – Capture ICMP traffic. - "udp port 53" – Capture UDP traffic on port 53. I also discovered that ICMP isn't just about ping! There are different message types, including type 17, 8, 3 and 0. πŸ˜… 2. Wireshark Display Filter Syntax – Used to filter traffic that has already been captured. Examples: - "dns" – Show DNS traffic. - "tcp" – Show TCP traffic. - "tcp.flags.syn == 1" – Show packets with the SYN flag set. - "frame.len > 1000" – Show packets larger than 1,000 bytes. I also explored Protocol, Application, Field Existence and Characteristics filters, which introduced me to something called BOOTP. Honestly, Field Existence and Characteristics filters gave me the hardest time. Still learning, still figuring things out. One packet at a time. πŸ˜„
Day 137 of my #EthicalHacking journey 🐍 Yesterday, I spent some time exploring #Python, particularly a module called "zipfile", which allows me to work with ZIP archives programmatically. I explored how to create, open, extract and manage compressed files. Out of curiosity, I also decided to explore "send2trash". What caught my attention was that instead of permanently deleting files, it sends them to the system's recycle bin or trash, just like when you normally delete something through the GUI. Didn't cover much yesterday, but I still got to explore something new and understand how these modules work. Not every day has to be packed with new concepts. Some days are just about getting a little further than you were yesterday. πŸ˜„ The journey continues!
2
9
2
28
897
One extra thing I am learning as I go deeper into web application is the ability to pay details to every information (response) you get from an application πŸ” some may lead to a dead end but most ignored signs and response leads to a possible exploit. Yesterday I got stuck solving this lab because I didn’t pay attention to the response the application was returning πŸ˜… While exploiting XXE to perform SSRF attack I was to locate a metadata endpoint, then the parser will pull the sensitive information, so all I had to do was point the parser to the right endpoint. I created the DTD, created the entity and pointed it to the metadata default URL but something was missing, the endpoint that had the sensitive information needed. When I made reference to the entity in the child element at first I didn’t see anything that looked like sensitive information, I spent sometime checking my payload and the structure over and over if there was something wrong till eventually I stopped and ended for the day πŸ›‘ Today I opened that lab again and while looking at the response I caught something πŸ‘€ the metadata service was returning its directory structure one path segment at a time, then you use that to build the full endpoint, at the first request the application reveal the first part of the endpoint β€œlatest” add this known endpoint to your URL and send the request the application will reveal the next endpoint, with this finding I was able to build the full URL for the metadata endpoint and view sensitive data about that metadata instance 🎯 When a response doesn’t match what you expect, don’t just re-check your payload, re-check your assumption that the response is useless. Sometimes the app is already telling you the next step. Solved another lab depending fully on my knowledge without using the solution button.
Today I started hands on lab on XXE injection and I just solved the first lab The application sends an XML request whenever a user wants to check a product stock availability. Going back to my theory lessons the 1 out of the 3 conditions that makes an XXE injection possible was present The application accepting XML from the user I modified the XML that was being sent to the server, added a DTD created an entity and pointed that entity to a file path on the server The parser processes the DTD and resolved the external entity, This was also tied back to my theory, for an XXE injection to be possible the application must accept XML from the user, process the DTD and resolve the external entities, all conditions were present in this lab. Creating a DTD and an external entity I was able to solve the lab and read the file content of /etc/passwd. XML and XXE are legitimate process, it goes wrong when the application start accepting XML from the user, processing the DTD and resolve external entities blindly
2
1
3
71
Day 138 of my #EthicalHacking journey. 🐧 Yesterday, I dove deeper into #Wireshark, learning two different filtering syntaxes. 1. BPF (Berkeley Packet Filter) – Used in Capture Filters to determine what traffic Wireshark captures. Examples: - "tcp port 80" – Capture TCP traffic on port 80. - "icmp" – Capture ICMP traffic. - "udp port 53" – Capture UDP traffic on port 53. I also discovered that ICMP isn't just about ping! There are different message types, including type 17, 8, 3 and 0. πŸ˜… 2. Wireshark Display Filter Syntax – Used to filter traffic that has already been captured. Examples: - "dns" – Show DNS traffic. - "tcp" – Show TCP traffic. - "tcp.flags.syn == 1" – Show packets with the SYN flag set. - "frame.len > 1000" – Show packets larger than 1,000 bytes. I also explored Protocol, Application, Field Existence and Characteristics filters, which introduced me to something called BOOTP. Honestly, Field Existence and Characteristics filters gave me the hardest time. Still learning, still figuring things out. One packet at a time. πŸ˜„
Day 137 of my #EthicalHacking journey 🐍 Yesterday, I spent some time exploring #Python, particularly a module called "zipfile", which allows me to work with ZIP archives programmatically. I explored how to create, open, extract and manage compressed files. Out of curiosity, I also decided to explore "send2trash". What caught my attention was that instead of permanently deleting files, it sends them to the system's recycle bin or trash, just like when you normally delete something through the GUI. Didn't cover much yesterday, but I still got to explore something new and understand how these modules work. Not every day has to be packed with new concepts. Some days are just about getting a little further than you were yesterday. πŸ˜„ The journey continues!
2
9
2
28
897
CYBERGEZ retweeted
If you could go back to your first days of learning cybersecurity, what's one thing you would do differently? Or what's something you wish someone had told you earlier? I'd love to hear from you. Someone starting out might also need to hear it. πŸ‘‡πŸΎ
Day 137 of my #EthicalHacking journey 🐍 Yesterday, I spent some time exploring #Python, particularly a module called "zipfile", which allows me to work with ZIP archives programmatically. I explored how to create, open, extract and manage compressed files. Out of curiosity, I also decided to explore "send2trash". What caught my attention was that instead of permanently deleting files, it sends them to the system's recycle bin or trash, just like when you normally delete something through the GUI. Didn't cover much yesterday, but I still got to explore something new and understand how these modules work. Not every day has to be packed with new concepts. Some days are just about getting a little further than you were yesterday. πŸ˜„ The journey continues!
1
8
1
18
478
If you could go back to your first days of learning cybersecurity, what's one thing you would do differently? Or what's something you wish someone had told you earlier? I'd love to hear from you. Someone starting out might also need to hear it. πŸ‘‡πŸΎ
Day 137 of my #EthicalHacking journey 🐍 Yesterday, I spent some time exploring #Python, particularly a module called "zipfile", which allows me to work with ZIP archives programmatically. I explored how to create, open, extract and manage compressed files. Out of curiosity, I also decided to explore "send2trash". What caught my attention was that instead of permanently deleting files, it sends them to the system's recycle bin or trash, just like when you normally delete something through the GUI. Didn't cover much yesterday, but I still got to explore something new and understand how these modules work. Not every day has to be packed with new concepts. Some days are just about getting a little further than you were yesterday. πŸ˜„ The journey continues!
1
8
1
18
478
CYBERGEZ retweeted
Have you ever wondered how #Wireshark captures network traffic? πŸ€” You open Wireshark, click Start, and suddenly you can see packets travelling across your network. But how does that actually happen? Let's break it down. 🧡
2
7
1
17
580
CYBERGEZ retweeted
Day 135 of my #EthicalHacking journey. Yesterday I mostly spent time practising what I'd learnt in #Wireshark. I revisited three exercises: - Capture Filters: Practised filtering out traffic from my own computer so I could focus on traffic coming from other devices. - Ring Buffer: Practised setting up continuous captures using a limited number of files, with older files automatically overwritten as new ones are created. This helps prevent capture files from consuming all available storage. - File Sets: Practised splitting captured traffic into smaller files based on size or time limits, rather than keeping everything in one massive file. Not every learning day has to involve something new. Sometimes, you need to go back and get comfortable with what you've already learnt. πŸ˜…
Day 134 of my #EthicalHacking journey Yesterday, I learnt how to identify when #Wireshark or even the network switch supplying it with traffic can't keep up. Wireshark uses a background process called "dumpcap" to capture packets. When traffic comes in faster than it can handle, packets may be dropped. One warning sign is the Dropped counter in the status bar. But here's the interesting part: when using a SPAN (port mirroring) configuration, the switch itself can drop packets before they even reach Wireshark. In that case, Wireshark might not report any dropped packets! One recommended solution is using a Network TAP, a dedicated hardware device that provides traffic copies for analysis. I also learnt about BPF (Berkeley Packet Filter) syntax, which is used to create capture filters and reduce the traffic Wireshark has to process. Turns out, sometimes the problem isn't the tool. It's what's feeding it. πŸ˜„
1
7
2
28
989