CaetanoBus A.I CyberSecurity Scoring
19/03/2026
Access Monitoring Plan
Access Monitoring Plan
No incidents recorded for CaetanoBus in 2026.
No incidents recorded for CaetanoBus in 2026.
No incidents recorded for CaetanoBus in 2026.
Automotive
Changan Automobile is among Top 4 Chinese automobile groups , with a history of 157 years, Changan Automobile has 35 years’ experience in auto-making. Changan has 16 production bases and 35 vehicle and engine plants globally. In 2014, total production and sales of Changan-branded vehicles exceeded 10 million. Changan’s production and sales volume in 2016 hit 3,000,000 units. By July of 2018, Changan-branded vehicle users have exceeded 17 million. Changan Automobile is committed to building world-class R&D capability. For 5 sessions in the past 10 years, Changan has been NO.1 in R&D capability in China’s automotive industry. Changan has over 12,000 R&D personnel from 18 countries, nearly 600 are senior experts, sitting at the forefront of China’s auto industry. We have built a globally collaborative R&D network with various priorities, connecting the R&D centers in Chongqing, Shanghai and Beijing of China, Turin of Italy, Yokohama of Japan, Nottingham of UK ,Detroit of USA and Munich of Germany. To ensure all products meet customers’ demand of driving for 10 years and 260,000 kilometers, Changan has established product development system and test validation system. In April 2018, Changan unveiled The Third Breakthrough-Innovation and Business Venture Program, with an aim to build a global leading automobile company. With this blueprint, Changan is committed to transforming itself into a leading technology company offering smart mobility solutions and services. The program expects to drive growth by innovation, enhance efficiency as the core competitiveness in organization, transform the company in four key areas and boost innovation in three fields. Changan Automobile has launched a series of classic products including CS series, EADO series, RAETON series and ect. With “hi-tech and trendy, efficient and clean, safe and smart” guiding product design, Changan has been vigorously developing new energy vehicles and intelligent vehicles.
Latest updates, reports, and threat intel affecting the global network.
"We provide real-time monitoring using artificial intelligence and we ensure potential breaches are fended off."
Graylog is a free and open log management platform. From 6.2.0 until 6.3.12, 7.0.7, and 7.1.2, the DELETE /users/{userId}/tokens/{idOrToken} endpoint implemented by UsersResource.revokeToken() in graylog2-server/src/main/java/org/graylog2/rest/resources/users/UsersResource.java checks USERS_TOKENREMOVE permission against the attacker-controlled userId path parameter before resolving the token selected by idOrToken. An authenticated user can provide an authorized userId while accessTokenService.loadById() or accessTokenService.load() resolves a token belonging to another user, including a service account or administrator, after which accessTokenService.destroy() deletes that token without checking AccessToken.getUserName(). The issue does not expose token contents, but unauthorized deletion causes integrity impact and can disrupt access-token-based integrations. This issue is fixed in versions 6.3.12, 7.0.7, and 7.1.2.
MariaDB Connector/R2DBC is a non-blocking MariaDB and MySQL client implemented in Java. Prior to 1.4.1, org.mariadb:r2dbc-mariadb does not gate clear-text password authentication plugins on transport encryption because the AuthenticationPlugin interface has no capability for a plugin to require a secure connection. A hostile or man-in-the-middle MariaDB server can send an AuthSwitchRequest naming mysql_clear_password or dialog (PAM) over a plain-TCP unencrypted connection, and AuthenticationFlow permits ClearPasswordPluginFlow or PamPluginFlow to return the user's password as cleartext bytes on the wire. The disclosed credentials can subsequently be used to authenticate directly to the database server. This issue is fixed in version 1.4.1.
MariaDB Connector/R2DBC is a non-blocking MariaDB and MySQL client implemented in Java. Prior to 1.4.1, org.mariadb:r2dbc-mariadb encodes and decodes all character data under the assumption that the connection character set is UTF-8. A server can announce a mid-session change to character_set_client through the OK-packet session-state-tracking mechanism, including through SET NAMES executed by a stored routine or trigger, server configuration, or a hostile or man-in-the-middle server. If the new character set is not UTF-8, the driver continues to exchange UTF-8 while the server interprets the same bytes under a different encoding, causing silent data corruption and a client/server charset-confusion mismatch that can defeat byte-wise quoting or escaping. The fix accepts only utf8, utf8mb3, or utf8mb4 after initialization; any other value raises R2dbcNonTransientResourceException with SQLState 08000 and closes the connection. This issue is fixed in version 1.4.1.
MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. Prior to 2.7.14, 3.3.5, 3.4.3, and 3.5.9, the connector encodes and decodes protocol text and performs client-side escaping under the assumption that the connection character set is UTF-8. The server can report a mid-session change to character_set_client through OK-packet session-state tracking, including a change caused by SET NAMES, a stored routine or trigger, server configuration, or a hostile server. If character_set_client changes to a non-UTF-8 value, the driver continues to read and write UTF-8 while the server interprets the same bytes under another encoding, causing silent data corruption and a client/server charset-confusion mismatch that can defeat byte-wise quoting or escaping. The fix accepts only utf8, utf8mb3, or utf8mb4 after initialization; any other value causes SQLException with SQLState 08000 and closes the connection. This issue is fixed in versions 2.7.14, 3.3.5, 3.4.3, and 3.5.9.
MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. Prior to 2.7.14, 3.3.5, 3.4.3, and 3.5.9, PAM dialog authentication can be coerced into transmitting the account password over an insecure connection. The mysql_clear_password plugin is gated behind a secure transport, but the sibling PAM handler SendPamAuthPacketFactory, named dialog by the server, does not declare that requirement and inherits the default secure-required value false; older branches implement the same affected behavior in SendPamAuthPacket. A hostile or man-in-the-middle server can send an Authentication Switch Request for dialog over plain TCP, causing the driver to return the user's password in cleartext when sslMode=DISABLE and restrictedAuth=null, which is the default configuration. Properly verified TLS and local Unix sockets are not exposed to this transport vector. This issue is fixed in versions 2.7.14, 3.3.5, 3.4.3, and 3.5.9.
curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?
linkedin_id=axa' -H 'apikey: YOUR_API_KEY_HERE'
Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.
Rankiteo is a unified scoring and risk platform that analyzes billions of signals weekly to help organizations gain faster, more actionable insights into emerging threats. Empowering teams to outpace adversaries and reduce exposure.