icy2003 /
php
| Conditions | 5 |
| Paths | 5 |
| Total Lines | 19 |
| Code Lines | 13 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 1 | ||
| Bugs | 0 | Features | 0 |
| 1 | <?php |
||
| 16 | public function decrypt($encryptedData, $iv, $sessionKey) |
||
| 17 | { |
||
| 18 | if (24 !== strlen($sessionKey)) { |
||
| 19 | throw new Exception('错误的 session key'); |
||
| 20 | } |
||
| 21 | if (24 !== strlen($iv)) { |
||
| 22 | throw new Exception('错误的 iv'); |
||
| 23 | } |
||
| 24 | $aesKey = base64_decode($sessionKey); |
||
| 25 | $aesIv = base64_decode($iv); |
||
| 26 | $aesCipher = base64_decode($encryptedData); |
||
| 27 | $this->_result = Json::decode(openssl_decrypt($aesCipher, 'aes-128-cbc', $aesKey, OPENSSL_RAW_DATA, $aesIv)); |
||
|
|
|||
| 28 | if (null === $this->_result) { |
||
| 29 | throw new Exception('错误的 encryptedData'); |
||
| 30 | } |
||
| 31 | if ($this->_result['watermark']['appid'] !== $this->_options['appid']) { |
||
| 32 | throw new Exception('错误的 appid'); |
||
| 33 | } |
||
| 34 | return $this; |
||
| 35 | } |
||
| 37 |
Our type inference engine has found a suspicous assignment of a value to a property. This check raises an issue when a value that can be of a mixed type is assigned to a property that is type hinted more strictly.
For example, imagine you have a variable
$accountIdthat can either hold an Id object or false (if there is no account id yet). Your code now assigns that value to theidproperty of an instance of theAccountclass. This class holds a proper account, so the id value must no longer be false.Either this assignment is in error or a type check should be added for that assignment.