| Package | Affected versions | Patched versions |
|---|---|---|
| laf | = 0.1.5= 0.4.0= 0.4.1= 0.4.10= 0.4.11= 0.4.12= 0.4.13= 0.4.14= 0.4.15= 0.4.16= 0.4.17= 0.4.18= 0.4.19= 0.4.2= 0.4.20= 0.4.21= 0.4.3= 0.4.4= 0.4.5= 0.4.6= 0.4.7= 0.4.8= 0.4.9= 0.5.0= 0.5.1= 0.5.2= 0.5.3= 0.5.4= 0.5.5= 0.5.6= 0.5.7= 0.5.8= 0.6.0= 0.6.1= 0.6.10= 0.6.11= 0.6.12= 0.6.13= 0.6.14= 0.6.15= 0.6.16= 0.6.17= 0.6.18= 0.6.19= 0.6.2= 0.6.20= 0.6.21= 0.6.22= 0.6.23= 0.6.3= 0.6.4= 0.6.5= 0.6.6= 0.6.7= 0.6.8= 0.6.9= 0.7.0= 0.7.1= 0.7.10= 0.7.11= 0.7.2= 0.7.3= 0.7.4= 0.7.5= 0.7.6= 0.7.7= 0.7.8= 0.7.9= 0.8.0= 0.8.1= 0.8.10= 0.8.11= 0.8.12= 0.8.13= 0.8.2= 0.8.3= 0.8.4= 0.8.5= 0.8.6= 0.8.7= 0.8.8= 0.8.9= 1.0.0 |
Laf is a cloud development platform. Prior to version 1.0.0-beta.13, the control of LAF app enV is not strict enough, and in certain scenarios of privatization environment, it may lead to sensitive information leakage in secret and configmap. In ES6 syntax, if an obj directly references another obj, the name of the obj itself will be used as the key, and the entire object structure will be integrated intact. When constructing the deployment instance of the app, env was found from the database and directly inserted into the template, resulting in controllability here. Sensitive information in the secret and configmap can be read through the k8s envFrom field. In a privatization environment, when `namespaceConf. fixed` is marked, it may lead to the leakage of sensitive information in the system. As of time of publication, it is unclear whether any patches or workarounds exist.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free