[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XD4EXHSJBHQWP9A7ZCY50E":3,"skill-same:01M6XD4EXHSJBHQWP9A7ZCY50E":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":13,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M6XD4EXHSJBHQWP9A7ZCY50E","jackson-security",null,"Security considerations for Jackson JSON deserialization in Java applications. Covers timing of validation, raw input interception, and common deserialization attack patterns.","Waaaalnut\u002Fskillsbench","Waaaalnut","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F103995656?v=4","01M6XCS9K1V51EY3JMB7DGMX24","01M6XCS9Q4WPW88W62C55G1H44",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FWaaaalnut\u002Fskillsbench\u002Fblob\u002Fmain\u002Ftasks-no-skills\u002Ffix-druid-loophole-cve\u002Fenvironment\u002Fskills\u002Fjackson-security\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30],"security","jackson","jackson security","validation","java","deserialization","applications","json","common","patterns","input","timing","for","2026-11-10 10:12:30",false,"---\nname: jackson-security\ndescription: Security considerations for Jackson JSON deserialization in Java applications. Covers timing of validation, raw input interception, and common deserialization attack patterns.\n---\n\n# Jackson Deserialization Security\n\n## Key Concept: Deserialization Timing\n\nJackson transforms JSON text into Java objects during a single `readValue()` call. This transformation is **not** a simple data copy—Jackson interprets JSON structure, resolves types, handles special keys, and instantiates objects all within this operation.\n\n    JSON String → [Jackson Processing] → Java Object\n                        ↑\n                Attack surface here\n\nOnce deserialization completes, the resulting Java object contains no trace of how it was constructed. Any special JSON structures, unusual keys, or type directives that influenced object creation are no longer visible.\n\n---\n\n## Why Post-Deserialization Validation Is Insufficient\n\nConsider the lifecycle of a typical JSON endpoint:\n\n    1. HTTP request arrives with JSON body\n    2. Framework deserializes JSON → Java object (Jackson runs here)\n    3. Your code receives the Java object\n    4. Your code validates the object\n    5. Your code processes the object\n\nValidation at step 4 examines the **result** of deserialization, not the **process**. Any malicious behavior triggered during step 2 has already executed. The Java object you're validating may appear completely normal while the attack has already succeeded.\n\nThis creates a fundamental blind spot: attacks that exploit Jackson's parsing behavior—rather than the final object state—cannot be detected by examining the deserialized object.\n\n---\n\n## The Empty Key (`\"\"`) Attack Vector\n\n### What Is It?\n\nJSON permits empty strings as object keys:\n\n    {\n      \"name\": \"legitimate\",\n      \"\": \"injected value\"\n    }\n\nThis is valid JSON per RFC 8259. Jackson parses it without error.\n\n### Why Does It Matter?\n\nSome applications and frameworks assign special meaning to empty keys:\n\n- **Injection points**: Certain Jackson configurations use `\"\"` to set values on the root object or trigger special handling\n- **Property override**: Empty keys may interact unexpectedly with `@JsonAnySetter` or custom deserializers\n- **Framework behaviors**: Some frameworks interpret `\"\"` as \"apply to parent\" or \"default target\"\n\n### The Visibility Problem\n\nAfter deserialization, there is no standard way to know an empty key was present:\n\n    \u002F\u002F Original JSON: {\"name\": \"test\", \"\": \"malicious\"}\n    MyObject obj = mapper.readValue(json, MyObject.class);\n    \u002F\u002F obj.getName() returns \"test\"\n    \u002F\u002F Where did \"\" go? Depends on configuration. You cannot tell from obj.\n\nThe attack's effectiveness depends on the specific Jackson configuration and target class—but the defender examining only the resulting object cannot determine whether `\"\"` was used.\n\n---\n\n## Other Structural Attack Patterns\n\n### Polymorphic Type Handling\n\nWhen Jackson is configured with `@JsonTypeInfo`, JSON can specify which class to instantiate:\n\n    {\n      \"@class\": \"com.attacker.MaliciousClass\",\n      \"command\": \"rm -rf \u002F\"\n    }\n\nJackson will attempt to instantiate whatever class is named. If the classpath contains exploitable \"gadget\" classes, arbitrary code execution may occur during deserialization—before your code ever runs.\n\nThe resulting object might be the expected type (if the attack class is a subtype), or deserialization might succeed partially before the damage is done.\n\n### Duplicate Keys\n\nJSON does not prohibit duplicate keys. Jackson's default behavior: **last value wins**.\n\n    {\n      \"role\": \"user\",\n      \"role\": \"admin\"\n    }\n\nJackson produces an object where `role` equals `\"admin\"`.\n\nIf upstream validation (like a WAF or input filter) checks only the first occurrence while Jackson uses the last, the validation and processing see different values.\n\n### Nested Injection\n\nDeeply nested structures can bypass depth-limited validation:\n\n    {\n      \"config\": {\n        \"settings\": {\n          \"internal\": {\n            \"\": \"payload\"\n          }\n        }\n      }\n    }\n\nSimple string checks might miss patterns buried in nested structures.\n","# Jackson Deserialization Security\n\n## Key Concept: Deserialization Timing\n\nJackson transforms JSON text into Java objects during a single `readValue()` call. This transformation is **not** a simple data copy—Jackson interprets JSON structure, resolves types, handles special keys, and instantiates objects all within this operation.\n\n    JSON String → [Jackson Processing] → Java Object\n                        ↑\n                Attack surface here\n\nOnce deserialization completes, the resulting Java object contains no trace of how it was constructed. Any special JSON structures, unusual keys, or type directives that influenced object creation are no longer visible.\n\n---\n\n## Why Post-Deserialization Validation Is Insufficient\n\nConsider the lifecycle of a typical JSON endpoint:\n\n    1. HTTP request arrives with JSON body\n    2. Framework deserializes JSON → Java object (Jackson runs here)\n    3. Your code receives the Java object\n    4. Your code validates the object\n    5. Your code processes the object\n\nValidation at step 4 examines the **result** of deserialization, not the **process**. Any malicious behavior triggered during step 2 has already executed. The Java object you're validating may appear completely normal while the attack has already succeeded.\n\nThis creates a fundamental blind spot: attacks that exploit Jackson's parsing behavior—rather than the final object state—cannot be detected by examining the deserialized object.\n\n---\n\n## The Empty Key (`\"\"`) Attack Vector\n\n### What Is It?\n\nJSON permits empty strings as object keys:\n\n    {\n      \"name\": \"legitimate\",\n      \"\": \"injected value\"\n    }\n\nThis is valid JSON per RFC 8259. Jackson parses it without error.\n\n### Why Does It Matter?\n\nSome applications and frameworks assign special meaning to empty keys:\n\n- **Injection points**: Certain Jackson configurations use `\"\"` to set values on the root object or trigger special handling\n- **Property override**: Empty keys may interact unexpectedly with `@JsonAnySetter` or custom deserializers\n- **Framework behaviors**: Some frameworks interpret `\"\"` as \"apply to parent\" or \"default target\"\n\n### The Visibility Problem\n\nAfter deserialization, there is no standard way to know an empty key was present:\n\n    \u002F\u002F Original JSON: {\"name\": \"test\", \"\": \"malicious\"}\n    MyObject obj = mapper.readValue(json, MyObject.class);\n    \u002F\u002F obj.getName() returns \"test\"\n    \u002F\u002F Where did \"\" go? Depends on configuration. You cannot tell from obj.\n\nThe attack's effectiveness depends on the specific Jackson configuration and target class—but the defender examining only the resulting object cannot determine whether `\"\"` was used.\n\n---\n\n## Other Structural Attack Patterns\n\n### Polymorphic Type Handling\n\nWhen Jackson is configured with `@JsonTypeInfo`, JSON can specify which class to instantiate:\n\n    {\n      \"@class\": \"com.attacker.MaliciousClass\",\n      \"command\": \"rm -rf \u002F\"\n    }\n\nJackson will attempt to instantiate whatever class is named. If the classpath contains exploitable \"gadget\" classes, arbitrary code execution may occur during deserialization—before your code ever runs.\n\nThe resulting object might be the expected type (if the attack class is a subtype), or deserialization might succeed partially before the damage is done.\n\n### Duplicate Keys\n\nJSON does not prohibit duplicate keys. Jackson's default behavior: **last value wins**.\n\n    {\n      \"role\": \"user\",\n      \"role\": \"admin\"\n    }\n\nJackson produces an object where `role` equals `\"admin\"`.\n\nIf upstream validation (like a WAF or input filter) checks only the first occurrence while Jackson uses the last, the validation and processing see different values.\n\n### Nested Injection\n\nDeeply nested structures can bypass depth-limited validation:\n\n    {\n      \"config\": {\n        \"settings\": {\n          \"internal\": {\n            \"\": \"payload\"\n          }\n        }\n      }\n    }\n\nSimple string checks might miss patterns buried in nested structures.\n",{"name":5,"description":7},"main","7eeb258ada72b7f58119b0e7a2c00ea89d9beedd","tasks-no-skills\u002Ffix-druid-loophole-cve\u002Fenvironment\u002Fskills\u002Fjackson-security","https:\u002F\u002Fgithub.com\u002FWaaaalnut\u002Fskillsbench","https:\u002F\u002Fgithub.com\u002FWaaaalnut","student of Zhejiang University","2026-04-21 23:16:23",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add Waaaalnut\u002Fskillsbench --skill jackson-security",{"tool":49,"command":50},"bunx","bunx skills add Waaaalnut\u002Fskillsbench --skill jackson-security",{"tool":52,"command":53},"pnpm","pnpm dlx skills add Waaaalnut\u002Fskillsbench --skill jackson-security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FWaaaalnut\u002Fskillsbench\u002Fblob\u002Fmain\u002Ftasks-no-skills\u002Ffix-druid-loophole-cve\u002Fenvironment\u002Fskills\u002Fjackson-security\u002FSKILL.md",true,[],[58,72,87,115,137,155],{"skillNo":59,"name":60,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":68,"publishedAt":31},"01M6XEWMJ6VY3ZC53MPDCPG3GH","data-reconciliation","https:\u002F\u002Fgithub.com\u002FWaaaalnut\u002Fskillsbench\u002Fblob\u002Fmain\u002Ftasks\u002Fxlsx-recover-data\u002Fenvironment\u002Fskills\u002Fdata-reconciliation\u002FSKILL.md",[63],{"categoryNo":64,"categoryName":65,"taxonomyType":66,"taxonomyTypeDesc":67},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[69,70,71],"data reconciliation","reconciliation","data",{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":31},"01M6XEW8MNPMF1KRXV6ATGFRQF","speech-to-text","Transcribe video to timestamped text using Whisper tiny model (pre-installed).","https:\u002F\u002Fgithub.com\u002FWaaaalnut\u002Fskillsbench\u002Fblob\u002Fmain\u002Ftasks\u002Fvideo-tutorial-indexer\u002Fenvironment\u002Fskills\u002Fspeech-to-text\u002FSKILL.md",[],[79,80,81,82,83,84,85,86],"speech","text","speech to text","transcribe video","whisper","model","Video","transcribe",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":98,"publishedAt":31},"01M6XEW3FQZP0T1RKQQJFXVY9T","video-processor","Process videos by removing segments and concatenating remaining parts. Use when you need to remove detected pauses\u002Fopenings from videos, create highlight reels, or batch process segment removals using ffmpeg filter_complex.","https:\u002F\u002Fgithub.com\u002FWaaaalnut\u002Fskillsbench\u002Fblob\u002Fmain\u002Ftasks\u002Fvideo-silence-remover\u002Fenvironment\u002Fskills\u002Fvideo-processor\u002FSKILL.md",[93],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[85,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114],"processor","video processor","batch","create","reels","when","parts","segments","process","videos","you","segment","filter","ffmpeg","use","remove",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":122,"publishedAt":31},"01M6XEVXJ5KZ0NTY3XZKRY4AS1","silence-detector","Detect initial silence segments in audio\u002Fvideo using energy-based analysis. Use when you need to find low-energy periods at the start of recordings (title slides, setup time, pre-roll silence).","https:\u002F\u002Fgithub.com\u002FWaaaalnut\u002Fskillsbench\u002Fblob\u002Fmain\u002Ftasks\u002Fvideo-silence-remover\u002Fenvironment\u002Fskills\u002Fsilence-detector\u002FSKILL.md",[121],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},[123,124,125,126,104,109,127,128,129,130,131,106,132,133,85,134,135,136,113],"detector","silence detector","title","slides","time","energy","at","recordings","detect","find","Audio","analysis","start","setup",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":31},"01M6XEVT3NGRN1FT7JPMAPXS6M","segment-combiner","Combine multiple segment detection results into a unified list. Use when you need to merge segments from different detectors, prepare removal lists for video processing, or consolidate detection outputs.","https:\u002F\u002Fgithub.com\u002FWaaaalnut\u002Fskillsbench\u002Fblob\u002Fmain\u002Ftasks\u002Fvideo-silence-remover\u002Fenvironment\u002Fskills\u002Fsegment-combiner\u002FSKILL.md",[],[110,144,85,145,146,147,148,30,104,149,150,106,109,151,152,113,153,154],"segment combiner","detection","prepare","merge","video processing","outputs","combine","processing","consolidate","results","list",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":164,"publishedAt":31},"01M6XEVMPVASGS2KX86QK4FMT7","report-generator","Generate compression reports for video processing. Use when you need to create structured JSON reports with duration statistics, compression ratios, and segment details after video processing.","https:\u002F\u002Fgithub.com\u002FWaaaalnut\u002Fskillsbench\u002Fblob\u002Fmain\u002Ftasks\u002Fvideo-silence-remover\u002Fenvironment\u002Fskills\u002Freport-generator\u002FSKILL.md",[161],{"categoryNo":162,"categoryName":163,"taxonomyType":66,"taxonomyTypeDesc":67},"01JBSEEDCAT000000000000034","行政与办公人员",[165,166,167,110,104,30,109,168,151,169,170,171,113,148,25,85,172,173,102],"generator","report generator","report","with","statistics","structured","reports","compression","generate"]