Issues in YamlEncoder.php (master) - Issues in master - fitbug/symfony-yaml-serializer-encoder-decoder - Measure and Improve Code Quality continuously with Scrutinizer

Issues (9)

Security Analysis no request data

Cross-Site Scripting

Cross-Site Scripting enables an attacker to inject code into the response of a web-request that is viewed by other users. It can for example be used to bypass access controls, or even to take over other users' accounts.

File Exposure

File Exposure allows an attacker to gain access to local files that he should not be able to access. These files can for example include database credentials, or other configuration files.

File Manipulation

File Manipulation enables an attacker to write custom data to files. This potentially leads to injection of arbitrary code on the server.

Object Injection

Object Injection enables an attacker to inject an object into PHP code, and can lead to arbitrary code execution, file exposure, or file manipulation attacks.

Code Injection

Code Injection enables an attacker to execute arbitrary code on the server.

Response Splitting

Response Splitting can be used to send arbitrary responses.

File Inclusion

File Inclusion enables an attacker to inject custom files into PHP's file loading mechanism, either explicitly passed to include, or for example via PHP's auto-loading mechanism.

Command Injection

Command Injection enables an attacker to inject a shell command that is execute with the privileges of the web-server. This can be used to expose sensitive data, or gain access of your server.

SQL Injection

SQL Injection enables an attacker to execute arbitrary SQL code on your database server gaining access to user data, or manipulating user data.

XPath Injection

XPath Injection enables an attacker to modify the parts of XML document that are read. If that XML document is for example used for authentication, this can lead to further vulnerabilities similar to SQL Injection.

LDAP Injection

LDAP Injection enables an attacker to inject LDAP statements potentially granting permission to run unauthorized queries, or modify content inside the LDAP tree.

Header Injection

Other Vulnerability

This category comprises other attack vectors such as manipulating the PHP runtime, loading custom extensions, freezing the runtime, or similar.

Regex Injection

Regex Injection enables an attacker to execute arbitrary code in your PHP process.

XML Injection

XML Injection enables an attacker to read files on your local filesystem including configuration files, or can be abused to freeze your web-server process.

Variable Injection

Variable Injection enables an attacker to overwrite program variables with custom data, and can lead to further vulnerabilities.

Unfortunately, the security analysis is currently not available for your project. If you are a non-commercial open-source project, please contact support to gain access.

src/YamlEncoder.php (3 issues)

Labels

Documentation 3

Severity

Informational 3

Upgrade to new PHP Analysis Engine

These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more

<?php


namespace Fitbug\SymfonySerializer\YamlEncoderDecoder;


use Symfony\Component\Serializer\Encoder\DecoderInterface;
use Symfony\Component\Serializer\Encoder\EncoderInterface;
use Symfony\Component\Serializer\Exception\UnexpectedValueException;

class YamlEncoder implements EncoderInterface, DecoderInterface
{
    /**
     * @var YamlEncode
     */
    private $yamlEncode;
    /**
     * @var YamlDecode
     */
    private $yamlDecode;

    /**
     * YamlEncoder constructor.
     *
     * @param YamlEncode $yamlEncodeImpl

     * @param YamlDecode $yamlDecodeImpl

     */
    public function __construct(YamlEncode $yamlEncodeImpl = null, YamlDecode $yamlDecodeImpl = null)
    {
        $this->yamlEncode = $yamlEncodeImpl ?: new YamlEncode();
        $this->yamlDecode = $yamlDecodeImpl ?: new YamlDecode();
    }


    /**
     * Decodes a string into PHP data.
     *
     * @param string $data    Data to decode
     * @param string $format  Format name
     * @param array  $context options that decoders have access to
     *
     * The format parameter specifies which format the data is in; valid values
     * depend on the specific implementation. This interface only supports YAML
     *
     * @return mixed

     *
     * @throws UnexpectedValueException
     */
    public function decode($data, $format, array $context = [])
    {
        return $this->yamlDecode->decode($data, $format, $context);
    }

    /**
     * Checks whether the deserializer can decode from given format.
     *
     * @param string $format format name
     *
     * @return bool
     */
    public function supportsDecoding($format)
    {
        return $this->yamlDecode->supportsDecoding($format);
    }

    /**
     * Encodes data into the given format.
     *
     * @param mixed  $data    Data to encode
     * @param string $format  Format name
     * @param array  $context options that normalizers/encoders have access to
     *
     * @return scalar
     *
     * @throws UnexpectedValueException
     */
    public function encode($data, $format, array $context = [])
    {
        return $this->yamlEncode->encode($data, $format, $context);
    }

    /**
     * Checks whether the serializer can encode to given format.
     *
     * @param string $format format name
     *
     * @return bool
     */
    public function supportsEncoding($format)
    {
        return $this->yamlEncode->supportsEncoding($format);
    }
}

1			<?php
2
3
4			namespace Fitbug\SymfonySerializer\YamlEncoderDecoder;
5
6
7			use Symfony\Component\Serializer\Encoder\DecoderInterface;
8			use Symfony\Component\Serializer\Encoder\EncoderInterface;
9			use Symfony\Component\Serializer\Exception\UnexpectedValueException;
10
11			class YamlEncoder implements EncoderInterface, DecoderInterface
12			{
13			/**
14			* @var YamlEncode
15			*/
16			private $yamlEncode;
17			/**
18			* @var YamlDecode
19			*/
20			private $yamlDecode;
21
22			/**
23			* YamlEncoder constructor.
24			*
25			* @param YamlEncode $yamlEncodeImpl
			0 ignored issues – show Documentation introduced 2016-08-12 11:27 UTC by Report Bug Copy Issue Report Show Similar Issues like this Should the type for parameter `$yamlEncodeImpl` not be `null\|YamlEncode`? This check looks for `@param` annotations where the type inferred by our type inference engine differs from the declared type. It makes a suggestion as to what type it considers more descriptive. Most often this is a case of a parameter that can be null in addition to its declared types. Loading history...
26			* @param YamlDecode $yamlDecodeImpl
			0 ignored issues – show Documentation introduced 2016-08-12 11:27 UTC by Report Bug Copy Issue Report Show Similar Issues like this Should the type for parameter `$yamlDecodeImpl` not be `null\|YamlDecode`? This check looks for `@param` annotations where the type inferred by our type inference engine differs from the declared type. It makes a suggestion as to what type it considers more descriptive. Most often this is a case of a parameter that can be null in addition to its declared types. Loading history...
27			*/
28			public function __construct(YamlEncode $yamlEncodeImpl = null, YamlDecode $yamlDecodeImpl = null)
29			{
30			$this->yamlEncode = $yamlEncodeImpl ?: new YamlEncode();
31			$this->yamlDecode = $yamlDecodeImpl ?: new YamlDecode();
32			}
33
34
35			/**
36			* Decodes a string into PHP data.
37			*
38			* @param string $data Data to decode
39			* @param string $format Format name
40			* @param array $context options that decoders have access to
41			*
42			* The format parameter specifies which format the data is in; valid values
43			* depend on the specific implementation. This interface only supports YAML
44			*
45			* @return mixed
			0 ignored issues – show Documentation introduced 2016-09-09 14:20 UTC by Report Bug Copy Issue Report Show Similar Issues like this Consider making the return type a bit more specific; maybe use `string\|array\|\stdClass`. This check looks for the generic type `array` as a return type and suggests a more specific type. This type is inferred from the actual code. Loading history...
46			*
47			* @throws UnexpectedValueException
48			*/
49			public function decode($data, $format, array $context = [])
50			{
51			return $this->yamlDecode->decode($data, $format, $context);
52			}
53
54			/**
55			* Checks whether the deserializer can decode from given format.
56			*
57			* @param string $format format name
58			*
59			* @return bool
60			*/
61			public function supportsDecoding($format)
62			{
63			return $this->yamlDecode->supportsDecoding($format);
64			}
65
66			/**
67			* Encodes data into the given format.
68			*
69			* @param mixed $data Data to encode
70			* @param string $format Format name
71			* @param array $context options that normalizers/encoders have access to
72			*
73			* @return scalar
74			*
75			* @throws UnexpectedValueException
76			*/
77			public function encode($data, $format, array $context = [])
78			{
79			return $this->yamlEncode->encode($data, $format, $context);
80			}
81
82			/**
83			* Checks whether the serializer can encode to given format.
84			*
85			* @param string $format format name
86			*
87			* @return bool
88			*/
89			public function supportsEncoding($format)
90			{
91			return $this->yamlEncode->supportsEncoding($format);
92			}
93			}

fitbug / symfony-yaml-serializer-encoder-decoder

Issues (9)

Security Analysis no request data

src/YamlEncoder.php (3 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like