Flutterby™! : Abuse of package managers

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

Abuse of package managers

2021-02-11 16:01:08.352184+00 by Dan Lyke 1 comments

Researcher hacks over 35 tech firms in novel supply chain attack

Birsan soon realized, should a dependency package used by an application exist in both a public open-source repository and your private build, the public package would get priority and be pulled instead -- without needing any action from the developer.

In some cases, as with PyPI packages, the researcher noticed that the package with the higher version would be prioritized regardless of wherever it was located.

Via https://mobile.twitter.com/hmemcpy/status/1359478493386592267

[ related topics: Current Events ]

comments in ascending chronological order (reverse):

#Comment Re: Abuse of package managers made: 2021-02-12 12:45:53.512528+00 by: DaveP

Somewhat similarly, I spent weeks chasing down a weird problem in ${PRODUCT} which turned out to be caused by one of our copies of node.js allocating an object, which then got freed by a different copy of node.js which was using a different allocator because reasons. That was about 2016 or 2017... One of the things I noticed along the way was that pieces-parts were being pulled from all over the internet, and if I firewalled off some less reputable sites, the build packaging would fail because one of the repositories couldn’t be reached. Mentioned it to the bosses, but never chased that observation down to “hey, we could pull the worng framework down.”

Oh well. Not the only problem I retired without solving...

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)

Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.