The MPTF Office supports UN coherence and the achievement of the Sustainable Development Goals with a well-designed and professionally managed portfolio of innovative pooled financing instruments.
Every day, we help millions of people to make journeys across London: By Tube, bus, tram, car, bike – and more. People don’t associate us with journeys by river, on foot or via the air, but we help with that, too. Getting people to where they need to go has been our business for over 100 years, and it shows. We’re leaders in our field, and no other city’s transport system is quite as recognisable: Red buses, black taxis, Tube trains and roundels have become icons in their own right. Our main job is to keep the city moving, working and growing but to do that, we have to listen. Constant improvements across the network are fuelled by feedback and comments from customers, as well as work within communities, representative groups, businesses and other London transport stakeholders. But our progress also depends on technology and data. With the future at our fingertips, we’ve already used it to revolutionise travel payments (think Oyster and contactless payment cards), and improved travel information. Tech and data is essential, not just to our future, but to others’: third parties use our data to power apps and services vital to customer journeys. So what’s next? As well as continuing to deliver Mayor of London, Sadiq Khan’s strategy and commitments on transport, our programme of capital investments is still one of the largest. We launched the Elizabeth line, we’re modernising services and stations and making travel safer for all.
Security & Compliance Standards Overview
UN Multi-Partner Trust Fund Office has 33.33% more incidents than the average of same-industry companies with at least one recorded incident.
Transport for London has 166.67% more incidents than the average of same-industry companies with at least one recorded incident.
UN Multi-Partner Trust Fund Office cyber incidents detection timeline including parent company and subsidiaries
Transport for London cyber incidents detection timeline including parent company and subsidiaries
Last 3 Security & Risk Events by Company
LibreChat is a ChatGPT clone with additional features. In versions 0.8.0 and below, there is no handler for JSON parsing errors; SyntaxError from express.json() includes user input in the error message, which gets reflected in responses. User input (including HTML/JavaScript) can be exposed in error responses, creating an XSS risk if Content-Type isn't strictly enforced. This issue does not have a fix at the time of publication.
LibreChat is a ChatGPT clone with additional features. In versions 0.8.0 and below, when creating prompts, JSON requests are sent to define and modify the prompts via PATCH endpoint for prompt groups (/api/prompts/groups/:groupId). However, the request bodies are not sufficiently validated for proper input, enabling users to modify prompts in a way that was not intended as part of the front end system. The patchPromptGroup function passes req.body directly to updatePromptGroup() without filtering sensitive fields. This issue is fixed in version 0.8.1.
LibreChat is a ChatGPT clone with additional features. In versions 0.8.0 and below, when a user posts a question, the iconURL parameter of the POST request can be modified by an attacker. The malicious code is then stored in the chat which can then be shared to other users. When sharing chats with a potentially malicious “tracker”, resources loaded can lead to loss of privacy for users who view the chat link that is sent to them. This issue is fixed in version 0.8.1.
MaxKB is an open-source AI assistant for enterprise. Versions 2.3.1 and below have improper file permissions which allow attackers to overwrite the built-in dynamic linker and other critical files, potentially resulting in privilege escalation. This issue is fixed in version 2.4.0.
MaxKB is an open-source AI assistant for enterprise. In versions 2.3.1 and below, the tool module allows an attacker to escape the sandbox environment and escalate privileges under certain concurrent conditions. This issue is fixed in version 2.4.0.
