titles workflow exposes the OpenAI key to a third-party action on every opened issue

Open Beginner friendly
#1,356 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions
Domain
ci-cd, security

Research direction

Start by inspecting the titles workflow and its opened-issue trigger, then trace how the OpenAI secret is passed to the third-party title action. Remove the reusable secret exposure while preserving the workflow's intended behavior, and verify that an issue opened by an untrusted account cannot provide the secret to that action.

Written by the indexing model from the issue text.

Description

Steps to reproduce

  1. Open an issue from an untrusted account.
  2. Inspect the titles workflow.

Actual result
The third-party title action receives the repository OpenAI secret.

Expected result
Avoid reusable secrets in an action triggered by issue creation.

Evidence
The workflow has the opened issue trigger and an OpenAI secret input.

Dominant language
JavaScript
Stars
36
Forks
64
Avg merge
1d 14h
Merged PRs (30d)
17

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 objectionary/eoc

All issues in objectionary/eoc

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.