Repository navigation
Conversation
RequireJS 2.3.6 is affected by CVE-2024-38999 (GHSA-x3m3-4wpv-5vgc), a prototype pollution flaw in require.config(). The fix, which skips the '__proto__' and 'constructor' keys when merging configuration objects, is the only functional change between 2.3.6 and 2.3.8. pgAdmin's local SonarQube clean-ups to require.js (renamed shadowed variables, an optional chain and a comment in an empty function) are carried forward unchanged. require.min.js, which base.html loads when DEBUG is off, has been regenerated from the updated require.js with uglify-js, as no upstream minified 2.3.8 build matches the previous one.
|
No actionable comments were generated in the recent review. WalkthroughThe vendored RequireJS file updates its version from 2.3.6 to 2.3.8. The update also changes ChangesRequireJS update
Estimated code review effort: 2 (Simple) | ~8 minutes Change: Other Merge Risk:
|
Updates the vendored RequireJS from 2.3.6 to 2.3.8 to fix CVE-2024-38999 (GHSA-x3m3-4wpv-5vgc), a prototype pollution flaw in
require.config().The only functional upstream change between the two versions is a guard in
eachProp()that skips the__proto__andconstructorkeys. pgAdmin's earlier SonarQube clean-ups torequire.jsare carried forward unchanged, andrequire.min.js(loaded bybase.htmlwhenDEBUGis off) has been regenerated from it with uglify-js.Checked in a Node
vmsandbox: the oldrequire.min.jsletsrequire.config()polluteObject.prototype, whilst both new files do not and still define and load modules normally.Summary by CodeRabbit