TheHive-Project / TheHive-Project/Cortex
Passwords stored in plaintext.
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.6k
- Forks
- 264
- PR merge metrics
- No merged PRs in 30d
Description
EDIT THIS TITLE BEFORE POSTING. Use this template for bug reports. If you'd like to request a feature, please be as descriptive as possible and delete the template except the first section (Request Type)
Request Type
Bug
Work Environment
| Question | Answer |
|---|---|
| OS version (server) | RHEL7 |
| OS version (client) | Win10 |
| Cortex version / git hash | 3.1.7-1 |
| Package Type | Docker |
| Browser type & version |
Problem Description
Sensitive data (private key and passwords in the configurations) are stored in an unencrypted manner on the Cortex component after being entered in a responder's configuration. Therefore, an attacker gaining access to this component can obtain all the secrets stored there. These passwords are only accessible to users with administrative rights, so the impact is limited.
Steps to Reproduce
- Log in with administrator account
- Make request to : /api/responder?range=all&sort=%2Bname
- You can see plaintext password frm responders configuration
Possible Solutions
Can you hash passwords before storing ?
Complementary information
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the /api/responder?range=all&sort=+name endpoint and reproduce the response using the administrator steps in the issue. Trace how responder configuration secrets are stored and serialized; done means passwords and private keys are not exposed in plaintext through this endpoint, with the security behavior covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100