oauth-labs - oauth-labs: an intentionally vulnerable set of OAu

项目说明


OAuth Labs

The main goal of OAuth labs is to learn more about OAuth, its defense
mechanisms and ways to exploit faulty implementations thereof.

The main theme of the labs is to obtain authorization to access the resources
of the admin user.

The labs ha that can be captured once the main has been
exploited. Each lab only contains one (known to us) which the
user is intended to exploit.

The labs can be solved in either a blackbox or whitebox approach. If the
whitebox approach is chosen, the user should read and analyze the source code
to locate and exploit the . Note however that *.sql files should
not be read because they contain the flag(s).

For each lab, you should start out by registering an account on the
authorization ser. Once you've set up your account, you can start
digging into the lab.

Getting started

To get started with the labs, you'll need to have the docker daemon running and
need to tweak your hosts file a little.

Note: The lab uses 172.16.16.0/24 as its subnet, ensure this doesn't
collide with your network.

Add the following hosts entries under /etc/hosts:

Once your hosts file is updated, go ahead and invoke the following commands to
clone, build, configure and spawn the labs:

Access the lab index under
Some of the labs require user interaction, you can find a simulator under

Commands

Below you'll find a list of commonly used commands.

Labs

Lab 00

This is just a playground, it is used as a base to build new labs by removing
or altering existing code. It shouldn't contain any flags or known
.

It may be used as a practical way to step through the requests to better
understand the authorization code flow and get a feel for the lab en.

Lab 01

+ ser.oauth.labs
+ client-01.oauth.labs

Claims fail; see what happens when a client implementation uses unstable claims
to establish a user identity.

Lab 02

+ ser.oauth.labs
+ client-02.oauth.labs

Open redirect (No restriction)
See what happens when the authorization server does not the
redirect_uri at all.

For this lab, .oauth.labs can be used to simulate interaction.

Lab 03

+ ser.oauth.labs
+ client-03.oauth.labs

Open redirect (relative path restriction) See what happens when the
authorization server only the redirect_uri domain.

For this lab, .oauth.labs can be used to simulate interaction.

Lab 04

+ ser.oauth.labs
+ client-04.oauth.labs

JWT signature are a must, see what happens when they are not .

Lab 05

+ ser.oauth.labs
+ client-05.oauth.labs

JWT signature done wrong, see what happens when jku claims are
not properly handled.

Help I'm stuck!

Callbacks

In case you get stuck on that one callback you just don't recei
you're using the gateway address 172.16.16.1 instead of localhost. Remember,
the labs are dockerized.

Use the source, Luke

Reading the source code may help you understand the problem you're having
better, don't shy away from cracking open your code editor and walking through
the code.

Nope, it's broken!

If all else fails, check back for walkthroughs or reach out. :)

References

Did you write a blog post, article or refer to oauth-labs in some shape or
form? Add it to our list of REFERENCES.md by forking and
opening a Pull request!

Licensing


This program is free software: you can redistribute it and/or modify it under the terms of the MIT license.

项目信息

开发语言：Go

Star 数：78

技术要点

该项目属于CTF思路方向的开源资源，代码结构清晰，适合安全研究人员学习参考。项目围绕oauth-labs: an intentionally vulnerable set of OAuth 2.0 labs for security training and learning展开，提供了可运行的实现，对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。

从技术实现角度看，此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论，梳理项目的初始化流程、核心模块职责与数据流转，逐步掌握其中的技术细节与设计思路。

使用与学习建议

1. 下载源码压缩包，解压到本地环境。

2. 根据项目类型准备对应的运行环境与依赖。

3. 按照 README 中的步骤完成配置与部署。

4. 在隔离的测试环境中运行验证，避免影响生产系统。

免责声明

本资源来源于开源社区，仅供安全研究、技术学习与合法授权范围内的攻防演练使用，请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。