タグ検索の該当結果が少ないため、タイトル検索結果を表示しています。
In association with the release of curl 8.4.0, we publish a security advisory and all the details for CVE-2023-38545. This problem is the worst security problem found in curl in a long time. We set it to severity HIGH. While the advisory contains all the necessary details. I figured I would use a few additional words and expand the explanations for anyone who cares to understand how this flaw work
SOCKS5 heap buffer overflow Project curl Security Advisory, October 11 2023 - Permalink VULNERABILITY This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass along the hostname to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that hostname can be is 255 bytes. If the hostname i
This summer, I upgraded a project from Node 18 to Node.js 20. The code was not that old, and I did not expect any problems... But as with every Node.js upgrade, unexpected behaviors happened. Why upgrade?It is common practice to keep projects up to date. Lagging behind too much may increase the work needed to upgrade when the choice isn’t yours anymore. I could have waited, but I had some time to
In this blog, I am going to explain the important concepts of Heap and use the ptmalloc in the Glibc 2.31 library as an example. The heap is a beautiful mess :) I really like the saying shown above. The word Heap we always use refers to the dynamically allocated segment in the virtual memory space of a process, but it actually stands for the implementation of the memory pool(the dynamic memory all
GitHub - facebook/memlab: A framework for finding JavaScript memory leaks and analyzing heap snapshots
memlab is an end-to-end testing and analysis framework for identifying JavaScript memory leaks and optimization opportunities. Online Resources: [Website and Demo] | [Documentation] | [Meta Engineering Blog Post] Features: Browser memory leak detection - Write test scenarios with the Puppeteer API, and memlab will automatically compare JavaScript heap snapshots, filter out memory leaks, and aggreg
FortiOS - heap-based buffer overflow in sslvpnd | PSIRT Advisories | FortiGuard
Explore latest research and threat reports on emerging cyber threats.
The answer is in your heap: debugging a big memory increase in Ruby on Rails | Island94.org
I recently participated in an interesting series of debugging sessions tracking down the source of a large increase in memory when upgrading a Rails application. We ultimately tracked down the cause using John Hawthorn’s Sheap heap analyzer and successfully submitted a patch to Rails. I thought it was interesting enough to write up because maybe the general approach to debugging memory issues woul
A trash heap 62 meters high shows the scale of India’s climate challenge | CNN
" data-check-event-based-preview="" data-is-vertical-video-embed="false" data-network-id="" data-publish-date="2022-12-09T09:54:59Z" data-video-section="world" data-canonical-url="https://www.cnn.com/videos/world/2022/12/09/india-bhalswa-landfill-pollution-climate-contd-intl-ldn-vpx.cnn" data-branding-key="" data-video-slug="india-bhalswa-landfill-pollution-climate-contd-intl-ldn-vpx" data-first-p
Memory management has always been a source of huge concern in Computer Science. Each piece of software is assigned a small portion of a computer’s finite memory; this memory has to be well-managed (carefully allocated and deallocated). With its efficient automatic garbage collection mechanism, Node.js tries to handle the tedious task of memory management and free up developers to work on other tas
Web Scraping via Javascript Runtime Heap Snapshots - Adrian Cooney's Blog
In recent years, the web has gotten very hostile to the lowly web scraper. It's a result of the natural progression of web technologies away from statically rendered pages to dynamic apps built with frameworks like React and CSS-in-JS. Developers no longer need to label their data with class-names or ids - it's only a courtesy to screen readers now. There's also been a concerted effort by large co
Show navigation This blog post has been authored by José Dapena Paz (Igalia), with contributions from Jason Williams (Bloomberg), Ashley Claymore (Bloomberg), Rob Palmer (Bloomberg), Joyee Cheung (Igalia), and Shu-yu Guo (Google). In this post about V8 heap snapshots, I will talk about some performance problems found by Bloomberg engineers, and how we fixed them to make JavaScript memory analysis
At V8, we're constantly striving to improve JavaScript performance. As part of this effort, we recently revisited the JetStream2 benchmark suite to eliminate performance cliffs. This post details a specific optimization we made that yielded a significant 2.5x improvement in the async-fs benchmark, contributing to a noticeable boost in the overall score. The optimization was inspired by the benchma
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
How I made a heap overflow in curl
curl - SOCKS5 heap buffer overflow - CVE-2023-38545
Node.js 20 upgrade: a journey through unexpected HEAP issues with Kubernetes
Understanding the Heap - a beautiful mess
Minimize Heap Allocations in Node.js | AppSignal Blog
Speeding up V8 heap snapshots · V8
Turbocharging V8 with mutable heap numbers · V8
xtech.nikkei.com
note.com/kininarukasetu
blog.livedoor.jp/reer121
www.youtube.com
diamond.jp
qiita.com/hyperfinitism