Technology

34889 readers

313 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.

Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.

Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 5 years ago

MODERATORS

[email protected]

Cloudflare's recent blog regarding polyfill shows that Cloudflare never authorized Polyfill to use their name in their product (blog.cloudflare.com)

submitted 4 months ago by [email protected] to c/[email protected]

12 comments fedilink hide all child comments

cross-posted from: https://programming.dev/post/16106778

Contrary to what is stated on the polyfill.io website, Cloudflare has never recommended the polyfill.io service or authorized their use of Cloudflare’s name on their website. We have asked them to remove the false statement, and they have, so far, ignored our requests. This is yet another warning sign that they cannot be trusted.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 11 points 4 months ago (4 children)

Direct linking via a specific CDN was the problem. This is solved by bundlers, not caused by it.

The polyfill.js is a popular open source library to support older browsers. 100K+ sites embed it using the cdn.polyfill.io domain. ... However, in February this year, a Chinese company bought the domain and the Github account. Since then, this domain was caught injecting malware on mobile devices via any site that embeds cdn.polyfill.io.

[–] [email protected] 2 points 4 months ago* (last edited 4 months ago) (3 children)

I read the story and specifically the bit about the Github account. Isn't this the Polyfill lib's Github account? Because if that's the case, how would a bundler solve the issue? The new owners could modify the original source, then the CICD jobs would happily publish that to registries and from there down into the bundles. Is it a different Github account they're talking about?

[–] [email protected] 4 points 4 months ago (2 children)

Code pulled from GitHub or NPM can be audited and it behaves consistently after it has been copied. If the code has a high reputation and gets incorporated into bundles, the code in the bundles doesn't change. If the project becomes malicious, only recently created bundles are affected. This code is pulled from polyfill.io every time somebody visits the page and recently polyfill.io has been hijacked to sometimes send malicious code instead. Websites that have been up for years can be affected by this.

[–] [email protected] 0 points 4 months ago (1 children)

Perfect. This is consistent with what I was thinking and that Cloudflare's changes won't fix any recent bundles that might include malicious code.

[–] [email protected] 1 points 4 months ago

Built bundles are not affected. The service is supposed to figure out which polyfills are required by a particular browser and serve different scripts. Because it's serving different scripts, the scripts cannot be bundled or secured using SRI. That would defeat the purpose of the service.