Uncaught Exception: "Cannot read properties of null (reading length)" when use encrypt function on lambda 20.x

[HeverFarber]

Problem:

When we change AWS lambda to nodejs20.x runtime - we start to get Uncaught Exception when we use encrypt function - after a big effort I figured out it came from a package stream-shift which uses a private field of the buffer. An issue has occurred on node 20.11.0, which affects the functionality of the lambda.

You are exposed to these uses because you depend on https://www.npmjs.com/package/duplexify version 4.1.1

Solution:

Update duplexify to version 4.1.3 which already fixes the version of stream-shift

[codyfrisch]

This issue just bit me as well.

[somersby10ml]

This issue just bit me as well.

[codyfrisch]

This issue just bit me as well.

I added overrides to my package.json. Probably overkill how I did it but did not want to leave any path open. I've also alerted someone I know at AWS to the current state of this project which seems to be "unmaintained" at this point. Or at least "forgotten about" someplace.

"overrides": {
    "@aws-crypto/encrypt-node@^4.0.0": {
        "duplexify": "^4.1.3"
    },
    "@aws-crypto/decrypt-node@^4.0.0": {
        "duplexify": "^4.1.3"
    },
    "@aws-crypto/client-node@^4.0.0": {
        "@aws-crypto/encrypt-node@^4.0.0": {
            "duplexify": "^4.1.3"
        },
        "@aws-crypto/decrypt-node@^4.0.0": {
            "duplexify": "^4.1.3"
        },
        "duplexify": "^4.1.3"
    },
    "duplexify": "^4.1.3"
}

[rekotiira]

Also affecting us - is nobody maintaining this library anymore?

[codyfrisch]

Also affecting us - is nobody maintaining this library anymore?

I do not believe this library should be considered active or usable in production going forward. Its clear it has been abandoned by AWS.

[ajewellamz]

A new release went out yesterday.
This library now support Node 16, 18, 20 and 22