Listed
archive-tar-minitar, minitar: archive-tar-minitar and minitar vulnerable to Path Traversal
It is on record here. It does not touch anything Phylax follows closely.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- archive-tar-minitar (RubyGems): every version, before 0.5.2
- minitar (RubyGems): every version, before 0.6
The fix
archive-tar-minitar (RubyGems) fixed in 0.5.2
bundlerbundle update --conservative archive-tar-minitarCheck what is installedbundle info archive-tar-minitarPaste into Cursor, Lovable or Claude CodeUpgrade the RubyGems dependency archive-tar-minitar to 0.5.2 or the nearest later release, to fix CVE-2016-10173. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.minitar (RubyGems) fixed in 0.6
bundlerbundle update --conservative minitarCheck what is installedbundle info minitarPaste into Cursor, Lovable or Claude CodeUpgrade the RubyGems dependency minitar to 0.6 or the nearest later release, to fix CVE-2016-10173. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "Listed".