Title: crypto,quic: missing NULL checks for OpenSSL allocation functions · Issue #62774 · nodejs/node · GitHub
Open Graph Title: crypto,quic: missing NULL checks for OpenSSL allocation functions · Issue #62774 · nodejs/node
X Title: crypto,quic: missing NULL checks for OpenSSL allocation functions · Issue #62774 · nodejs/node
Description: Version v22.13.1 Platform A container based on Ubuntu 22.04 OS Subsystem crypto, quic What steps will reproduce the bug? This is a set of latent defects found by static analysis (Svace), not a runtime-reproducible bug. The issues are: sr...
Open Graph Description: Version v22.13.1 Platform A container based on Ubuntu 22.04 OS Subsystem crypto, quic What steps will reproduce the bug? This is a set of latent defects found by static analysis (Svace), not a runt...
X Description: Version v22.13.1 Platform A container based on Ubuntu 22.04 OS Subsystem crypto, quic What steps will reproduce the bug? This is a set of latent defects found by static analysis (Svace), not a runt...
Opengraph URL: https://github.com/nodejs/node/issues/62774
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"crypto,quic: missing NULL checks for OpenSSL allocation functions","articleBody":"### Version\n\nv22.13.1\n\n### Platform\n\n```text\nA container based on Ubuntu 22.04 OS\n```\n\n### Subsystem\n\ncrypto, quic\n\n### What steps will reproduce the bug?\n\nThis is a set of latent defects found by static analysis (Svace), not\na runtime-reproducible bug. The issues are:\n\n1. src/crypto/crypto_aes.cc, function AES_Cipher (line 46):\n EVP_CIPHER_CTX_new() result used without NULL check.\n Cross-file statistics: checked in 37 of 40 call sites.\n\n2. src/crypto/crypto_aes.cc, function AES_CTR_Cipher2 (line 225):\n EVP_CIPHER_CTX_new() result used without NULL check.\n Same detector, same function.\n\n3. src/crypto/crypto_ec.cc, function ECKeyExportTraits::DoExport \n (line 1264): EC_KEY_new() result used without NULL check.\n Cross-file statistics: checked in 5 of 6 call sites.\n\n4. src/quic/tlscontext.cc, function TLSSession::Initialize (line 2051):\n SSL_new() result used without NULL check.\n Cross-file statistics: checked in 9 of 10 call sites.\n\n5. src/crypto/crypto_cipher.cc, function CipherBase::CommonInit\n (line 2570): EVP_CIPHER_CTX_new() result wrapped in unique_ptr\n and used without verifying it's non-null.\n\n### How often does it reproduce? Is there a required condition?\n\nWould manifest under memory pressure when OpenSSL fails to allocate\ninternal structures. Not trivially reproducible in normal operation.\n\n### What is the expected behavior? Why is that the expected behavior?\n\nAllocation failures should result in a controlled error (thrown\nJavaScript exception or appropriate error status), not a NULL pointer\ndereference / segmentation fault.\n\n### What do you see instead?\n\nPotential SIGSEGV on allocation failure.\n\n### Additional information\n\nThese findings come from the ISPRAS open-source static analysis\nworking group. All issues are of the same class (OpenSSL allocation\nfunction return value used without NULL check) and can be fixed\ntogether.","author":{"url":"https://github.com/UnLucky252","@type":"Person","name":"UnLucky252"},"datePublished":"2026-04-16T13:26:36.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/62774/node/issues/62774"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:4a933a62-3741-0228-472e-99c89f2b17b2 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | BD56:29EB19:22B2AF:2F6A59:6A4D5875 |
| html-safe-nonce | afbba8faaca617bc7677f193af819ef3330cc7542454c1d7d36d9c8decd58690 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCRDU2OjI5RUIxOToyMkIyQUY6MkY2QTU5OjZBNEQ1ODc1IiwidmlzaXRvcl9pZCI6IjgyNzgwMjIxNDQ3ODk5MzUyNSIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 6bbb72301bf23dc4d19aefc79e970c29a49be2cab0ce0e850417ac7b310bb885 |
| hovercard-subject-tag | issue:4276019032 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/nodejs/node/62774/issue_layout |
| twitter:image | https://opengraph.githubassets.com/691e3aaff8ebc10b93213e811d9cb021649ae44bb0728aa5fc697e65a91b4f1d/nodejs/node/issues/62774 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/691e3aaff8ebc10b93213e811d9cb021649ae44bb0728aa5fc697e65a91b4f1d/nodejs/node/issues/62774 |
| og:image:alt | Version v22.13.1 Platform A container based on Ubuntu 22.04 OS Subsystem crypto, quic What steps will reproduce the bug? This is a set of latent defects found by static analysis (Svace), not a runt... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | UnLucky252 |
| hostname | github.com |
| expected-hostname | github.com |
| None | 2a1443ff9733a3016431263ea73c93d8fe00c195eb4a7670ac30e7848f045441 |
| turbo-cache-control | no-preview |
| go-import | github.com/nodejs/node git https://github.com/nodejs/node.git |
| octolytics-dimension-user_id | 9950313 |
| octolytics-dimension-user_login | nodejs |
| octolytics-dimension-repository_id | 27193779 |
| octolytics-dimension-repository_nwo | nodejs/node |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 27193779 |
| octolytics-dimension-repository_network_root_nwo | nodejs/node |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | f3bdd3157ea1f0fd738d408eceeead721acf1dc3 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width