GiteaApplication
CVE-2018-15192
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn SSRF vulnerability in webhooks in Gitea through 1.5.0-rc2 and Gogs through 0.11.53 allows remote attackers to access intranet services.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn SSRF (Server-Side Request Forgery) vulnerability in the webhook functionality of Gitea (versions up to 1.5.0-rc2) and Gogs (versions up to 0.11.53) allows remote attackers to make the server perform arbitrary HTTP requests to internal/intranet services by manipulating webhook URL parameters.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GiteaApplication
< 1.5.0= 1.5.0<= 0.11.53CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Gitea or Gogs is runningCheck running processes for gitea or gogs binaries, or check Docker containers if deployed as containersAffected if Either Gitea or Gogs process/container is running on the system
-
Determine installed Gitea versionAccess the Gitea admin dashboard and navigate to the Site Administration page to view the version, or query the Gitea API endpoint /api/v1/version if availableAffected if Gitea version is less than 1.5.0 or equals 1.5.0 (any version below 1.5.0 is affected)
-
Determine installed Gogs versionAccess the Gogs admin dashboard and navigate to the Site Administration page to view the version, or query the Gogs version through the admin interfaceAffected if Gogs version is 0.11.53 or lower (0.11.53 and all prior versions are affected)
-
Verify webhook functionality is enabledCheck if the webhook feature is accessible by navigating to repository settings and looking for the Webhooks section, or check the configuration file for webhook-related settingsAffected if Webhook functionality is enabled and accessible to users (the SSRF requires this feature to be available)
-
Confirm server has network access capabilityReview the Gitea or Gogs configuration file (app.ini for Gitea, custom/conf/app.ini for Gogs) for HTTP settings and verify the server process has outbound network accessAffected if The server can make outbound HTTP requests (this is required for the SSRF to be exploitable)
You are affected if you are running Gitea version 1.5.0 or any version below 1.5.0, or Gogs version 0.11.53 or below, and the webhook feature is enabled on your installation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.5.0
Upgrade Gitea to version 1.5.0 or later and Gogs to version 0.12.0 or later. Additionally, implement network segmentation and restrict outbound access from the Git server to internal network ranges.
Fix this in Gitea
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15192 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-15192 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data