Merge pull request #7 from CyberLions/dan

Dan

Author: 23younesm

Pwn/Overflow/challenge.yml

@@ -0,0 +1,103 @@
+# This file represents the base specification of your challenge. It is used by
+# other tools to install and deploy your challenge.
+
+# Required sections
+name: "Overflow"
+author: "Daniel Feliciano @DaZ-CYBER"
+category: Pwn
+description: |
+  This is my first C program in Computer Science! My teacher told me to make sure I don't use some old functions, like strcpy(), strmem(), and...there's one more that I forgot.... oh well!
+#value: 30
+type: dynamic
+
+extra:
+    initial: 500
+    decay: 30
+    minimum: 100
+
+# The extra field provides additional fields for data during the install/sync commands/
+# Fields in extra can be used to supply additional information for other challenge types
+# For example the follow extra field is for dynamic challenges. To use these following
+# extra fields, set the type to "dynamic" and uncomment the "extra" section below
+# extra:
+#     initial: 500
+#     decay: 100
+#     minimum: 50
+
+# Settings used for Dockerfile deployment
+# If not used, remove or set to null
+# If you have a Dockerfile set to .
+# If you have an imaged hosted on Docker set to the image url (e.g. python/3.8:latest, registry.gitlab.com/python/3.8:latest)
+# Follow Docker best practices and assign a tag
+image: .
+# Specify a host to deploy the challenge onto.
+# The currently supported URI schemes are ssh:// and registry://
+# ssh is an ssh URI where the above image will be copied to and deployed (e.g. ssh://root@123.123.123.123)
+# registry is a Docker registry tag (e.g registry://registry.example.com/test/image)
+# host can also be specified during the deploy process: `ctf challenge deploy challenge --host=ssh://root@123.123.123.123`
+host: null
+
+# Optional settings
+
+# connection_info is used to provide a link, hostname, or instructions on how to connect to a challenge
+# connection_info: https://icespice-silly-ctf.psuccso.org/
+
+# healthcheck is a tool/script used to check a challenge
+# If connection_info was provided to CTFd when the challenge was installed, it will be passed to the healthcheck script:
+# ./writeup/exploit.sh --connection-info "nc hostname 12345"
+# healthcheck: writeup/exploit.sh
+
+# Can be removed if unused
+# attempts: 5
+
+# Flags specify answers that your challenge use. You should generally provide at least one.
+# Can be removed if unused
+# Accepts strings or dictionaries of CTFd API data
+flags:
+    # A static case sensitive flag
+    - {
+        type: "static",
+        content: "CCSO{mY_F1R$T_0V3RFL0W!}",
+        data: "case_insensitive",
+    }
+    - {
+        type: "static",
+        content: "Overflow",
+        data: "case_insensitive",
+    }
+# Topics are used to help tell what techniques/information a challenge involves
+# They are generally only visible to admins
+# Accepts strings
+#topics:
+#    - icespice
+
+# Tags are used to provide additional public tagging to a challenge
+# Can be removed if unused
+# Accepts strings
+tags:
+    - Pwn
+    - Easy
+
+# Provide paths to files from the same directory that this file is in
+# Accepts strings
+#files:
+
+# Hints are used to give players a way to buy or have suggestions. They are not
+# required but can be nice.
+# Can be removed if unused
+# Accepts dictionaries or strings
+#hints:
+#    - {
+#        content: "Awww you gyatta give that page some Hawk Tuah and SQL on dat thang!",
+#        cost: 2
+#    }
+
+
+# The state of the challenge.
+# If the field is omitted, the challenge is visible by default.
+# If provided, the field can take one of two values: hidden, visible.
+state: visible
+
+# Specifies what version of the challenge specification was used.
+# Subject to change until ctfcli v1.0.0
+version: "0.1"

Pwn/Overflow/src/Connection-Instructions.txt

@@ -0,0 +1,17 @@
+Connection Instructions
+========================
+Use the following information to connect to each challenge container.
+If you experience any connection issues, please contact a system administrator for assistance.
+Note: Sometimes a port might be busy; if so, try another available port.
+
+Overflow Containers (Public IP:Port -> Container Name):
+- 132.145.211.121:3000 -> overflow-container-1
+- 132.145.211.121:3001 -> overflow-container-2
+- 132.145.211.121:3002 -> overflow-container-3
+- 132.145.211.121:3003 -> overflow-container-4
+- 132.145.211.121:3004 -> overflow-container-5
+- 132.145.211.121:3005 -> overflow-container-6
+- 132.145.211.121:3006 -> overflow-container-7
+- 132.145.211.121:3007 -> overflow-container-8
+- 132.145.211.121:3008 -> overflow-container-9
+- 132.145.211.121:3009 -> overflow-container-10