GHSA-X477-FQ37-Q5WR
Vulnerability from github – Published: 2023-01-27 00:55 – Updated: 2023-01-27 00:55Impact
version 1.5.0 and 1.6.0 when using the new debug-host feature could expose unnecessary information about the host
Patches
Use 1.6.1 or newer
Workarounds
Downgrade to 1.4.0 or set debug-host to empty
References
https://github.com/fortio/proxy/pull/38
Q&A https://github.com/fortio/proxy/discussions
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "fortio.org/proxy"
},
"ranges": [
{
"events": [
{
"introduced": "1.5.0"
},
{
"fixed": "1.6.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-200"
],
"github_reviewed": true,
"github_reviewed_at": "2023-01-27T00:55:27Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "### Impact\nversion 1.5.0 and 1.6.0 when using the new `debug-host` feature could expose unnecessary information about the host\n\n### Patches\nUse 1.6.1 or newer\n\n### Workarounds\nDowngrade to 1.4.0 or set `debug-host` to empty\n\n### References\nhttps://github.com/fortio/proxy/pull/38\n\nQ\u0026A https://github.com/fortio/proxy/discussions",
"id": "GHSA-x477-fq37-q5wr",
"modified": "2023-01-27T00:55:27Z",
"published": "2023-01-27T00:55:27Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/fortio/proxy/security/advisories/GHSA-x477-fq37-q5wr"
},
{
"type": "WEB",
"url": "https://github.com/fortio/proxy/pull/38"
},
{
"type": "PACKAGE",
"url": "https://github.com/fortio/proxy"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "Initial debug-host handler implementation could leak information and facilitate denial of service"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.