Sanitize user inputs or replace `sed` usage

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
security

Research direction

Inspect the command construction at rust/operator-binary/src/command.rs:47 and the Kerberos-related code at rust/operator-binary/src/kerberos.rs:95. Trace how user-controlled values reach sed, then verify both locations sanitize inputs or no longer rely on sed and that the affected command behavior remains correct.

Written by the indexing model from the issue text.

Description

Two places:

https://github.com/stackabletech/hive-operator/blob/5f9d0b7aa8ab9f718e019d8286fc700016aaddc7/rust/operator-binary/src/command.rs#L47

https://github.com/stackabletech/hive-operator/blob/5f9d0b7aa8ab9f718e019d8286fc700016aaddc7/rust/operator-binary/src/kerberos.rs#L95

Dominant language
Rust
Stars
29
Forks
2
Avg merge
1d 19h
Merged PRs (30d)
12

Contributor guide

No contributing guide indexed for this repository

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 stackabletech/hive-operator

All issues in stackabletech/hive-operator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.