vulnerability / NVI-00003604 / Revision 1
Possibility for Denial of Service by overwriting PHP files with language exports
OSV carries this publisher advisory for barryvdh/laravel-translation-manager. This is an aggregated source copy; consult the original publisher and compare update dates.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
barryvdh/laravel-translation-manager
source listedECOSYSTEM: introduced 0; fixed 0.6.2
### 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
03 / Response
What to do next
- vendor patch
The original advisory lists fixed boundaries 0.6.2 for barryvdh/laravel-translation-manager. Confirm the publisher’s latest guidance.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-3fvf-2gp4-89wq ↗
GitHub Advisory Database via OSV · vendor advisory
Observed . GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.