<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://jjeuribe.github.io/</id><title>Javier Uribe</title><subtitle>Sharing what I learn in cybersecurity and software engineering along the way.</subtitle> <updated>2026-05-26T13:00:06-06:00</updated> <author> <name>Javier Uribe</name> <uri>https://jjeuribe.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://jjeuribe.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://jjeuribe.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Javier Uribe </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>OOP - Classes - The Clay That Shapes Your Software</title><link href="https://jjeuribe.github.io/posts/oop-classes-the-clay-that-shapes-your-software/" rel="alternate" type="text/html" title="OOP - Classes - The Clay That Shapes Your Software" /><published>2026-05-26T07:00:00-06:00</published> <updated>2026-05-26T07:00:00-06:00</updated> <id>https://jjeuribe.github.io/posts/oop-classes-the-clay-that-shapes-your-software/</id> <content type="text/html" src="https://jjeuribe.github.io/posts/oop-classes-the-clay-that-shapes-your-software/" /> <author> <name>Javier Uribe</name> </author> <category term="Software Design" /> <category term="OOP" /> <summary>I’ve always seen OOP (Object-Oriented Programming) as the closest thing developers have to playing God. You essentially create worlds from scratch, you’re constantly shaping a small version of reality inside your software: A banking system has accounts, transactions, and customers. A game has players, weapons, missions, and enemies. An e-commerce platform has carts, products, and orders. This i...</summary> </entry> <entry><title>AWS Pentesting - Flaws Level 6 - When the Gateway Finally Falls</title><link href="https://jjeuribe.github.io/posts/aws-pentesting-flaws-level-6-when-the-gateway-finally-falls/" rel="alternate" type="text/html" title="AWS Pentesting - Flaws Level 6 - When the Gateway Finally Falls" /><published>2026-04-28T07:00:00-06:00</published> <updated>2026-04-28T07:00:00-06:00</updated> <id>https://jjeuribe.github.io/posts/aws-pentesting-flaws-level-6-when-the-gateway-finally-falls/</id> <content type="text/html" src="https://jjeuribe.github.io/posts/aws-pentesting-flaws-level-6-when-the-gateway-finally-falls/" /> <author> <name>Javier Uribe</name> </author> <category term="Cybersecurity" /> <category term="Red Team" /> <summary>In this final challenge, you’re given an AWS access key with limited (mostly read-only) permissions. No admin powers, no obvious misconfigurations, this time just pure old-school enumeration. Your job is to explore the account, follow the clues, and pay attention to the details. The more you dig, the more patterns will start to show up. Observation will be your most powerful weapon here. Alrig...</summary> </entry> <entry><title>AWS Pentesting - Flaws Level 5 - Exploiting AWS IMDS via SSRF</title><link href="https://jjeuribe.github.io/posts/aws-pentesting-flaws-level-5-exploiting-aws-imds-via-ssrf/" rel="alternate" type="text/html" title="AWS Pentesting - Flaws Level 5 - Exploiting AWS IMDS via SSRF" /><published>2026-04-28T06:00:00-06:00</published> <updated>2026-04-28T06:00:00-06:00</updated> <id>https://jjeuribe.github.io/posts/aws-pentesting-flaws-level-5-exploiting-aws-imds-via-ssrf/</id> <content type="text/html" src="https://jjeuribe.github.io/posts/aws-pentesting-flaws-level-5-exploiting-aws-imds-via-ssrf/" /> <author> <name>Javier Uribe</name> </author> <category term="Cybersecurity" /> <category term="Red Team" /> <summary>In this level, you’ll deal with a proxy feature that’s letting an attacker to fetch external resources on behalf of one of your EC2 instances. This may not look dangerous at first, but under the hood it opens the door to a very well-known vulnerability. That said, let’s take a look at the challenge scenario: Scenario: This EC2 has a simple HTTP only proxy on it. Here are some examples of i...</summary> </entry> <entry><title>AWS Pentesting - Flaws Level 4 - When EBS Snapshots Leak Secrets</title><link href="https://jjeuribe.github.io/posts/aws-pentesting-flaws-level-4-when-ebs-snapshots-leak-secrets/" rel="alternate" type="text/html" title="AWS Pentesting - Flaws Level 4 - When EBS Snapshots Leak Secrets" /><published>2026-04-28T05:00:00-06:00</published> <updated>2026-04-28T05:00:00-06:00</updated> <id>https://jjeuribe.github.io/posts/aws-pentesting-flaws-level-4-when-ebs-snapshots-leak-secrets/</id> <content type="text/html" src="https://jjeuribe.github.io/posts/aws-pentesting-flaws-level-4-when-ebs-snapshots-leak-secrets/" /> <author> <name>Javier Uribe</name> </author> <category term="Cybersecurity" /> <category term="Red Team" /> <summary>In this level, your objective is to gain access to a web application. A URL will be provided, and you must authenticate using a valid username and password. The challenge introduces you the following scenario: Scenario: For the next level, you need to get access to the web page running on an EC2 http://4d0cf09b9b2d761a7d87be99d17507bce8b86f3b.flaws.cloud. It’ll be useful to know that a sna...</summary> </entry> <entry><title>AWS Pentesting - Flaws Level 3 - From Public Bucket to AWS Keys</title><link href="https://jjeuribe.github.io/posts/aws-pentesting-flaws-level-3-from-public-bucket-to-aws-keys/" rel="alternate" type="text/html" title="AWS Pentesting - Flaws Level 3 - From Public Bucket to AWS Keys" /><published>2026-04-27T07:00:00-06:00</published> <updated>2026-04-27T07:00:00-06:00</updated> <id>https://jjeuribe.github.io/posts/aws-pentesting-flaws-level-3-from-public-bucket-to-aws-keys/</id> <content type="text/html" src="https://jjeuribe.github.io/posts/aws-pentesting-flaws-level-3-from-public-bucket-to-aws-keys/" /> <author> <name>Javier Uribe</name> </author> <category term="Cybersecurity" /> <category term="Red Team" /> <summary>Continuing with our S3 bucket exposure journey, this challenge introduces the following scenario: Scenario: The next level is fairly similar, with a slight twist. Time to find your first AWS key! I bet you’ll find something that will let you list what other buckets are. Ok, the instructions are crystal clear: find an AWS key pair and use it to list the buckets accessible with those creden...</summary> </entry> </feed>
