Add Historical Examples of Exploits / Compromises

Open
#14 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
elixir

Research direction

Review the existing security modules, starting with the lesson about disallowing code evaluation in Elixir. Find relevant CVEs, public compromises, or bug-bounty reports and add concise links that contextualize each insecurity. The work is done when the applicable modules have useful historical examples without changing the lesson guidance.

Written by the indexing model from the issue text.

Description

new content small adjustment

I think it would be super cool to start adding to the various insecurities throughout the modules historical examples of CVEs, public compromises/incidents, etc.

It could be as simple as a link out to other reading, but it could help contextualize the impact and reach a particular issue has in a broader sense.

Example: For the lesson on not allowing code eval in Elixir, link out to maybe an incident a company has had or bug bounty find that allowed for remote code execution.

Dominant language
Elixir
Stars
732
Forks
172
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from erlef/elixir-secure-coding

All issues in erlef/elixir-secure-coding

Similar issues

More Elixir issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.