Possibility for Denial of Service by overwriting PHP files with language exports
The advisory, in context
Impact
Laravel Translation Manager didn't check the locale name, which allowed directory traversal when exporting files. The content would be a PHP file returning an array of translations, but this could lead to unexpected results, like denial of service. Access to the Laravel Translation Manager is required, because a new locale would have to be added and published.
Patches
Version 0.6.2 fixes this issue.
Workarounds
Only allow trusted admins to publish/edit translations.
References
https://github.com/barryvdh/laravel-translation-manager/pull/417
For more information
If you have any questions or comments about this advisory:
- Open an issue in https://github.com/barryvdh/laravel-translation-manager
- Email me (see Github profile)
Credits
Found and reported by Natalia Trojanowska
Affected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
Earlier releases before 0.6.2
Fixed in 0.6.2
32 explicitly affected versions
v0.1.0, v0.1.1, v0.1.2, v0.1.3, v0.1.4, v0.2.0, v0.2.1, v0.2.2, v0.2.3, v0.2.4, v0.2.5, v0.2.6, v0.2.7, v0.2.8, v0.2.9, v0.3.0, v0.4.0, v0.4.1, v0.4.2, v0.5.0, v0.5.1, v0.5.10, v0.5.2, v0.5.3, v0.5.4, v0.5.5, v0.5.6, v0.5.7, v0.5.8, v0.5.9, v0.6.0, v0.6.1
View affected-version evidence
{
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.6.2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"v0.1.0",
"v0.1.1",
"v0.1.2",
"v0.1.3",
"v0.1.4",
"v0.2.0",
"v0.2.1",
"v0.2.2",
"v0.2.3",
"v0.2.4",
"v0.2.5",
"v0.2.6",
"v0.2.7",
"v0.2.8",
"v0.2.9",
"v0.3.0",
"v0.4.0",
"v0.4.1",
"v0.4.2",
"v0.5.0",
"v0.5.1",
"v0.5.10",
"v0.5.2",
"v0.5.3",
"v0.5.4",
"v0.5.5",
"v0.5.6",
"v0.5.7",
"v0.5.8",
"v0.5.9",
"v0.6.0",
"v0.6.1"
]
}