haskellcamargo/gemidao-do-zap

Token utilizado por terceiros

Open

#48 opened on Aug 10, 2017

View on GitHub
 (10 comments) (0 reactions) (0 assignees)JavaScript (1,995 stars) (200 forks)batch import
help wanted

Description

Seguinte, dei 5 baits do gemidão.

Sai pra uma entrevista, quando voltei estou com saldo negativo R$-0,15. Alguém (não sei como, pois não mandei meu token pra ngm) usou meu token em DDD 63. Espero não ser mandado pro SPC/Serasa

Contributor guide

Tech stack
javascriptnodejs
Domain
clisecurity
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Basic understanding of Node.jsFamiliarity with token management
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate how authentication tokens are generated and stored in the repository. Look at the source code in the likely file 'index.js' or similar to identify where tokens are used and how they might be leaked. The issue mentions a token used by a third party without the user's knowledge, suggesting a potential security vulnerability (e.g., token exposure in logs or network requests). Check for any existing discussions or comments that might indicate the root cause. Since this is an old issue without recent activity, a maintainer may need to provide additional context on the intended token handling.