For your digest
trytond: Tryton Improper Access Control
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
trytond (PyPI)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- trytond (PyPI): from 4.2.0, before 4.2.21
- trytond (PyPI): from 4.4.0, before 4.4.19
- trytond (PyPI): from 4.6.0, before 4.6.14
- trytond (PyPI): from 4.8.0, before 4.8.10
- trytond (PyPI): from 5.0.0, before 5.0.6
- trytond (PyPI): from 4.2.0, before 4.2.21; from 4.4.0, before 4.4.19; from 4.6.0, before 4.6.14; from 4.8.0, before 4.8.10; from 5.0.0, before 5.0.6
The fix
trytond (PyPI) fixed in 4.2.21
pippython -m pip install trytond==4.2.21uvuv add trytond==4.2.21poetrypoetry add trytond@4.2.21Check what is installedpython -m pip show trytondPaste into Cursor, Lovable or Claude CodeUpgrade the PyPI dependency trytond to 4.2.21 or the nearest later release, to fix CVE-2019-10868. 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.trytond (PyPI) fixed in 4.4.19
pippython -m pip install trytond==4.4.19uvuv add trytond==4.4.19poetrypoetry add trytond@4.4.19Check what is installedpython -m pip show trytondPaste into Cursor, Lovable or Claude CodeUpgrade the PyPI dependency trytond to 4.4.19 or the nearest later release, to fix CVE-2019-10868. 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.trytond (PyPI) fixed in 4.6.14
pippython -m pip install trytond==4.6.14uvuv add trytond==4.6.14poetrypoetry add trytond@4.6.14Check what is installedpython -m pip show trytondPaste into Cursor, Lovable or Claude CodeUpgrade the PyPI dependency trytond to 4.6.14 or the nearest later release, to fix CVE-2019-10868. 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.trytond (PyPI) fixed in 4.8.10
pippython -m pip install trytond==4.8.10uvuv add trytond==4.8.10poetrypoetry add trytond@4.8.10Check what is installedpython -m pip show trytondPaste into Cursor, Lovable or Claude CodeUpgrade the PyPI dependency trytond to 4.8.10 or the nearest later release, to fix CVE-2019-10868. 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.trytond (PyPI) fixed in 5.0.6
pippython -m pip install trytond==5.0.6uvuv add trytond==5.0.6poetrypoetry add trytond@5.0.6Check what is installedpython -m pip show trytondPaste into Cursor, Lovable or Claude CodeUpgrade the PyPI dependency trytond to 5.0.6 or the nearest later release, to fix CVE-2019-10868. 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 "For your digest".