Security readout for executives and security teams
Plain-English summary
This CVE describes an open redirect in flask-oidc 0.1.2 and earlier. In affected applications, a user may be redirected to an unintended external site during an authentication-related flow. The source bundle does not provide a severity score, patch version, or evidence of active exploitation.
Executive priority
Treat this as a targeted authentication-flow hygiene issue. Prioritize systems using affected flask-oidc versions on public login paths, but do not assume emergency exploitation without more evidence.
Technical view
The CVE record identifies flask-oidc 0.1.2 and earlier as vulnerable to open redirect behavior, with a reference to flask_oidc/__init__.py. Available sources do not include CVSS, CWE mapping, affected CPEs, a named fixed version, or exploit-in-the-wild evidence.
Likely exposure
Exposure is most likely in Python web applications that depend on flask-oidc 0.1.2 or earlier, especially where OIDC login, logout, or return-url flows are internet-facing.
Exploitation context
The provided sources support an open redirect finding only. They do not show public exploitation, KEV listing, weaponized details, or confirmed impact beyond redirection risk.
Researcher notes
Evidence is sparse: the CVE description names only flask-oidc 0.1.2 and earlier, and the bundle includes no CVSS, CWE, CPE, patch advisory, or KEV signal. Validate dependency presence before assessing business impact.
Mitigation direction
- Inventory applications and SBOMs for flask-oidc 0.1.2 or earlier.
- Check project or vendor guidance for a fixed release or supported migration path.
- Restrict authentication redirects to relative paths or explicitly approved hosts.
- Add regression tests covering rejected off-domain redirect destinations.
Validation and detection
- Search dependency manifests for flask-oidc and recorded deployed versions.
- Review OIDC login and logout flows for externally controlled redirect destinations.
- Confirm redirect allowlists reject untrusted domains in test environments.
- Check runtime package versions across production, staging, and container images.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2016-1000001 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/puiterwijk/flask-oidc/blob/master/flask_oidc/__init__.py#L293CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.