Skip to content

Potential security vulnerability with Flask version #212

@fossell

Description

@fossell

Describe the Task

Need to investigate potential security risk with our version of Flask. Recommended to use > v2.2.5. we know v3.2 broke the API (see #203). Looks like some of those issues were closed, so could try latest again and see if it works now.

Time Estimate

1 day

Sub-Issues

Consider breaking the task down into sub-issues.

  • Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required
  • Select scientist(s) or no scientist required

Labels

  • Select component(s)
  • Select priority

Projects and Milestone

  • Select Project
  • Select Milestone as the next official version or Backlog of Development Ideas

Task Checklist

  • Complete the issue definition above, including the Time Estimate.
  • Fork this repository or create a branch of develop.
    Branch name: feature_<Issue Number>/<Description>
  • Complete the development and test your changes.
  • Add/update log messages for easier debugging.
  • Add/update tests.
  • Add/update documentation.
  • Push local changes to GitHub.
  • Submit a pull request to merge into develop.
    Pull request: feature <Issue Number> <Description>
  • Define the pull request metadata, as permissions allow.
    Select: Reviewer(s), Project, and Development issue
    Select: Milestone as the next official version
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions