Security readout for executives and security teams
Plain-English summary
Older Gitea versions accepted a specially malformed Git remote path containing a port and encoded newline characters. The source bundle does not state the business impact, but malformed repository input can affect systems that accept user-supplied repository URLs. Treat this as an upgrade and exposure-review item for any self-hosted Gitea deployment.
Executive priority
Prioritize remediation for exposed or multi-user Gitea services. The absence of severity scoring and exploitation evidence lowers confidence in urgency, but the vulnerable range is old and has a clear fixed release.
Technical view
CVE-2020-28991 is in Gitea's ParseRemoteAddr logic in modules/auth/repo_form.go. Versions 0.9.99 through 1.12.x before 1.12.6 did not block a git protocol path that included both a TCP port number and URL-encoded newlines.
Likely exposure
Exposure is limited to Gitea deployments running 0.9.99 through 1.12.x before 1.12.6, especially where untrusted or low-privilege users can submit remote Git repository addresses to Gitea-controlled workflows.
Exploitation context
The provided sources do not show CISA KEV listing, active exploitation, public exploit maturity, CVSS, or CWE classification. They only identify the affected version range, vulnerable parsing behavior, and a Gitea 1.12.6 release reference.
Researcher notes
The bundle supports a narrow finding: insufficient validation of a Git protocol path containing a port and URL-encoded newlines. It does not establish impact, exploitability, attacker privileges, or affected deployment paths beyond Gitea version range.
Mitigation direction
- Upgrade affected Gitea instances to version 1.12.6 or later.
- Review Gitea release notes and PR 13525 for vendor-specific guidance.
- Inventory any internet-facing or user-facing Gitea instances.
- Restrict repository remote-address submission to trusted users until upgraded.
- Check vendor guidance before applying non-vendor workarounds.
Validation and detection
- Confirm the running Gitea version is 1.12.6 or later.
- Identify whether repository remote-address parsing features are available to untrusted users.
- Review change management records for the Gitea 1.12.6 upgrade.
- Check logs for unusual failed repository remote submissions, without testing exploit payloads.
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-2020-28991 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/go-gitea/gitea/pull/13525CVE reference · x_refsource_MISC
- https://github.com/go-gitea/gitea/releases/tag/v1.12.6CVE 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.