home.social

#deserialization — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #deserialization, aggregated by home.social.

  1. 🚀 Wow! A 5-minute epic on how rearranging some #structs 🏗️ in #Rust saves a whopping 475 MB of #memory. Who knew struct feng shui could revolutionize #JSON deserialization? 🙄 Next up, "How I Saved The World by Organizing My Sock Drawer." 🧦
    dystroy.org/blog/box-to-save-m #Optimization #Deserialization #HackerNews #TechHumor #HackerNews #ngated

  2. 🚀 Wow! A 5-minute epic on how rearranging some #structs 🏗️ in #Rust saves a whopping 475 MB of #memory. Who knew struct feng shui could revolutionize #JSON deserialization? 🙄 Next up, "How I Saved The World by Organizing My Sock Drawer." 🧦
    dystroy.org/blog/box-to-save-m #Optimization #Deserialization #HackerNews #TechHumor #HackerNews #ngated

  3. 🚀 Wow! A 5-minute epic on how rearranging some #structs 🏗️ in #Rust saves a whopping 475 MB of #memory. Who knew struct feng shui could revolutionize #JSON deserialization? 🙄 Next up, "How I Saved The World by Organizing My Sock Drawer." 🧦
    dystroy.org/blog/box-to-save-m #Optimization #Deserialization #HackerNews #TechHumor #HackerNews #ngated

  4. 🚀 Wow! A 5-minute epic on how rearranging some #structs 🏗️ in #Rust saves a whopping 475 MB of #memory. Who knew struct feng shui could revolutionize #JSON deserialization? 🙄 Next up, "How I Saved The World by Organizing My Sock Drawer." 🧦
    dystroy.org/blog/box-to-save-m #Optimization #Deserialization #HackerNews #TechHumor #HackerNews #ngated

  5. Using JsonPropertyName to map Json to Class C# Tip #42 - How to use the [JsonPropertyName] attribute in C# to map mismatched JSON fields (like "id") to class properties (like UniquePostId) during deserialization. #CSharp #JSON #Deserialization #HttpClient #JsonPropertyName #DataMapping #WebAPI #DotNet #Attributes

  6. 🚀 Nächste Woche ist #BaselOne24 🎉

    Am 16. und 17. Oktober 2024 erwarten Euch viele spannende Workshops und Vorträge von bekannten Speaker:innen und Newcomer:innen. Dabei bringen Sie Euch auf den neuesten Stand in Sachen #KünstlicheIntelligenz, #Deserialization, #Metriken, #TeamBuilding, #Java, #Kafka, #Testing, und vieles mehr.

    👉🏻 Hier geht's zum Programm: lnkd.in/egfakuP5

    🐸 lnkd.in/ggjmzerN

    #communityrocks #BaselOne #TechEvent #CleanCode #AI #Kafka #Java

  7. ⏳Wer hat an der Uhr gedreht... Nur noch 3 Wochen bis zur #BaselOne24... 😊

    🔊 Am 16. und 17. Oktober 2024 erwarten Euch Gerrit Grunwald, Grace Jansen, Falk Sippach, Nadine Broghammer, Simon Martinelli und Patrick Baumgartner. Dabei bringen Sie Euch auf den neuesten Stand in Sachen #KünstlicheIntelligenz, #Deserialization, #Metriken, #TeamBuilding, hashtag#Java, #Kafka, #Testing, und vieles mehr.

    🐸 unter lnkd.in/ggjmzerN.

    #Communityrocks #SoftwareDevelopment #TechConference #AI

  8. Critical Kibana Vulnerability - Arbitrary Code Execution via YAML Deserialization

    Date: September 5, 2024

    CVE: CVE-2024-37285

    Vulnerability Type: Deserialization of Untrusted Data

    CWE: [[CWE-502]]

    Sources: Elastic Security Advisory

    Synopsis

    CVE-2024-37285 impacts Kibana versions 8.10.0 to 8.15.0, where a deserialization flaw allows remote code execution if an attacker injects malicious YAML payloads. This vulnerability requires that an attacker has elevated Elasticsearch and Kibana privileges.

    Issue Summary

    The vulnerability arises from improper YAML deserialization within Kibana. A malicious actor can craft a YAML payload and execute arbitrary code, provided they have specific Elasticsearch index and Kibana privileges. This issue affects Kibana from versions 8.10.0 through 8.15.0 and is critical due to its ease of exploitation and the potential for widespread impact.

    Technical Key Findings

    Attackers exploit this flaw by submitting a specially crafted YAML document that Kibana deserializes without proper validation. Once the malicious code is parsed, it can run on the server with elevated privileges, enabling arbitrary code execution.

    The attacker must have the following Elasticsearch indices permissions;

    • write access to system indices .kibana_ingest*
    • The allow_restricted_indices flag needs to be set to true

    The attacker must also have ANY of the following Kibana privileges;

    • Under Fleet the All privilege is granted
    • Under Integration the Read or All privilege is granted
    • Access to the fleet-setup privilege is gained through the Fleet Server’s service account token## Vulnerable Products
    • Kibana versions 8.10.0 to 8.15.0.

    Impact Assessment

    Successful exploitation could allow an attacker to execute arbitrary commands, leading to a complete system compromise. This could affect confidentiality, integrity, and availability, making it a high-risk issue for organizations relying on Kibana for data visualization and exploration.

    Patches or Workaround

    Upgrading to Kibana version 8.15.1 resolves this vulnerability. Additionally, limiting access to Elasticsearch indices and restricting Kibana privileges reduces exposure.

    Tags

    #CVE-2024-37285 #Kibana #ArbitraryCodeExecution #YAML #Deserialization #ElasticStack #CyberSecurity