GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Security Vulnerability Disclosure · Issue #3684 · feast-dev/feast

Security Vulnerability Disclosure #3684

New issue
Copy link
New issue
Copy link
Closed
#3978
Closed
Security Vulnerability Disclosure#3684
#3978
Copy link
Labels
kind/bugpriority/p0Highest priorityHighest priority

Description

@AdnaneKhan
AdnaneKhan
opened on Jul 14, 2023
Issue body actions

I've found a security issue with this repository, how can I privately disclose this?

Activity

  1. AdnaneKhan
    added
    kind/bug
    priority/p2
    on Jul 14, 2023
  2. shuchu commented on Jul 15, 2023

    @shuchu
    shuchu
    on Jul 15, 2023
    Collaborator
    More actions

    there is a slack channel:
    http://slack.feast.dev/
    And you can msg Danny (@adchia)

  3. AdnaneKhan commented on Sep 13, 2023

    @AdnaneKhan
    AdnaneKhan
    on Sep 13, 2023
    Author
    More actions

    Hey! sorry this got away from me - I re-checked and the vuln is still here. Got an email address I can send it to? Kind of a pain to join lots of Slack channels. Thankfully fix is really simple.

  4. jeremyary commented on Feb 27, 2024

    @jeremyary
    jeremyary
    on Feb 27, 2024
    Collaborator
    More actions

    @AdnaneKhan if you'd still like to disclose with us, we can be reached collectively at [email protected], but should you prefer further discretion, please feel free to reach out to me directly at [email protected] & I'd be happy to serve as conduit in raising the issue with our other maintainers. Thanks!

  5. jeremyary
    closed this as completedon Feb 27, 2024
  6. AdnaneKhan commented on Feb 28, 2024

    @AdnaneKhan
    AdnaneKhan
    on Feb 28, 2024
    Author
    More actions

    @AdnaneKhan if you'd still like to disclose with us, we can be reached collectively at [email protected], but should you prefer further discretion, please feel free to reach out to me directly at [email protected] & I'd be happy to serve as conduit in raising the issue with our other maintainers. Thanks!

    I sent an email to your Redhat address. The group mail didn't work for some reason (I got a delivery failure notification).

  7. jeremyary commented on Feb 28, 2024

    @jeremyary
    jeremyary
    on Feb 28, 2024
    Collaborator
    More actions

    @AdnaneKhan received! I appreciate you taking the time to share this with me, I'm putting it on my own list to tackle.

  8. jeremyary
    reopened this on Feb 28, 2024
  9. jeremyary
    added
    priority/p0Highest priorityHighest priority
    and removed
    priority/p2
    on Feb 28, 2024
  10. franciscojavierarceo
    closed this as completedin #3978on Feb 29, 2024
  11. ntkathole
    added a commit that references this issue on Aug 6, 2026

    docs: Add a security policy (#6692)

    e8edab5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugpriority/p0Highest priorityHighest priority

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.