GHSA-4r78-hx75-jjj2 CVE-2018-17847 CVE-2018-17848 GHSA-mv93-wvcp-7m7r GO-2022-0197
golang.org/x/net/html has Improper Restriction of Operations within the Bounds of a Memory Buffer
High
Go
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 2.36%
- Chance of exploitation in the next 30 days. Higher than 83.80% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
- Fix
0.0.0-20190125002852-4b62a64f59f7- Upgrade golang.org/x/net to this version or later
Description
The html package (aka x/net/html) through 2018-09-25 in Go mishandles <svg><template><desc><t><svg></template>, leading to a panic: runtime error (index out of range) in (*nodeStack).pop in node.go, called from (*parser).clearActiveFormattingElements, during an html.Parse call.
Affected versions
Go
| Package | Vulnerable | Fixed in |
|---|---|---|
| golang.org/x/net | < 0.0.0-20190125002852-4b62a64f59f7 |
0.0.0-20190125002852-4b62a64f59f7 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
golang.org/x/net Go → 0.0.0-20190125002852-4b62a64f59f7
- go
go get golang.org/x/net@v0.0.0-20190125002852-4b62a64f59f7 && go mod tidy
Severity breakdown
CVSS 3.1 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Weakness
CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
How to prevent it
- Requirements: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega [REF-57], and the Strsafe.h library from Microsoft [REF-56]. These libraries provide safer versions of overflow-prone string-handling functions.
- Operation, Build and Compilation: Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
- Implementation: Consider adhering to the following rules when allocating and managing an application's memory: Double check that the buffer is as large as specified. When using functions that accept a number of bytes to copy, such as strncpy(), be aware that if the destination buffer size is equal to the source buffer size, it may not NULL-terminate the string. Check buffer boundaries if accessing the buffer in a loop and make sure there is no danger of writing past the allocated space. If necessary, truncate all input strings to a reasonable length before passing them to the copy and concatenation functions.
- Operation, Build and Compilation: Run or compile the software using features or extensions that randomly arrange the positions of a program's executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code. Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as "rebasing" (for Windows) and "prelinking" (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking. For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].
- Operation: Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX [REF-60] [REF-61]. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment. For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND [REF-1336].
- Implementation: Replace unbounded copy functions with analogous functions that support length arguments, such as strcpy with strncpy. Create these if they are not available.
References
Advisories
Packages
Other links
- github.com/golang/go/issues/27846
- go.dev/cl/159397
- go.dev/issue/27846
- go.googlesource.com/net/+/4b62a64f59f73840b9ab79204c94fee61cd1ba2c
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LREEW…
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UKRCI…
- pkg.go.dev/vuln/GO-2022-0197
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-4374-p667-p6c8 HTTP/2 rapid reset can cause excessive work in net/http | High Known exploited | Also affects golang.org/x/net |
| GHSA-qppj-fm5r-hxr3 HTTP/2 Stream Cancellation Attack | Medium Known exploited | Also affects golang.org/x/net |
| GO-2026-6866 Check all ancestor namespace transitions when rendering raw text in html in golang.org/x/net | Not rated yet | Also affects golang.org/x/net |
| GO-2026-6860 Avoid quadratic complexity when coalescing text nodes in html in golang.org/x/net | Not rated yet | Also affects golang.org/x/net |
| GO-2026-6617 HTTP/2 server crash due to HPACK encoder race in net/http | High | Also affects golang.org/x/net |
| GO-2026-6612 Double flow control refund on HTTP/2 server streams in net/http | Critical | Also affects golang.org/x/net |
| GO-2026-6611 Excessive CPU consumption from repeated initial window changes in net/http | High | Also affects golang.org/x/net |
| GO-2026-6610 HTTP/2 transport accepts malformed framing-related headers in net/http | High | Also affects golang.org/x/net |
Credits: @tr3ee
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor