izm1chael commited on
Commit
8335c56
·
verified ·
1 Parent(s): aebc61c

Publish Layerfault deep challenge LF-CH-HUBLFS-0010

Browse files
CHALLENGE_ORACLE.json ADDED
@@ -0,0 +1,33 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "attack_surface": [
3
+ "hub-lfs-state"
4
+ ],
5
+ "control_type": "negative",
6
+ "corpus_id": "LF-CH-HUBLFS-0010",
7
+ "difficulty": "adversarial",
8
+ "expected_decision": "PASS",
9
+ "ground_truth": "synthetic-generated",
10
+ "layerfault_rule_expectations": {
11
+ "candidate_rules": [],
12
+ "expected_rules": [],
13
+ "must_not_rules": [
14
+ "LF-HUB-LFS-OID-INVALID",
15
+ "LF-HUB-LFS-SIZE-MISMATCH"
16
+ ]
17
+ },
18
+ "oracle_ids": [
19
+ "LF-ORACLE-HUBLFS-0010"
20
+ ],
21
+ "related_cases": [],
22
+ "repo_name": "hub-lfs-doc-pointer-control",
23
+ "safe_fixture": true,
24
+ "schema": 2,
25
+ "severity": "informational",
26
+ "techniques": [
27
+ "lfs",
28
+ "doc",
29
+ "pointer",
30
+ "control"
31
+ ],
32
+ "transformations": []
33
+ }
FIXTURE_LAYOUT.json ADDED
@@ -0,0 +1,8 @@
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "artifacts": [
3
+ "README.md"
4
+ ],
5
+ "family": "hublfs",
6
+ "note": "All content is synthetic and inert. Do not treat this as a production model.",
7
+ "repo_name": "hub-lfs-doc-pointer-control"
8
+ }
LAYERFAULT_CORPUS.json ADDED
@@ -0,0 +1,41 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "candidate_rules": [],
3
+ "challenge": {
4
+ "attack_surface": [
5
+ "hub-lfs-state"
6
+ ],
7
+ "control_type": "negative",
8
+ "difficulty": "adversarial",
9
+ "expected_decision": "PASS",
10
+ "oracle_ids": [
11
+ "LF-ORACLE-HUBLFS-0010"
12
+ ],
13
+ "related_cases": [],
14
+ "severity": "informational",
15
+ "techniques": [
16
+ "lfs",
17
+ "doc",
18
+ "pointer",
19
+ "control"
20
+ ],
21
+ "transformations": []
22
+ },
23
+ "corpus_id": "LF-CH-HUBLFS-0010",
24
+ "description": "Hub lfs doc pointer control.",
25
+ "expected_rules": [],
26
+ "generator": "challenges.generate_challenge",
27
+ "ground_truth": "synthetic-generated",
28
+ "must_not_rules": [
29
+ "LF-HUB-LFS-OID-INVALID",
30
+ "LF-HUB-LFS-SIZE-MISMATCH"
31
+ ],
32
+ "repo_name": "hub-lfs-doc-pointer-control",
33
+ "repo_type": "model",
34
+ "safe_fixture": true,
35
+ "safety": "inert/canary-only",
36
+ "schema": 1,
37
+ "validation": {
38
+ "kind": "verify-package",
39
+ "target": "."
40
+ }
41
+ }
README.md ADDED
@@ -0,0 +1,74 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ license: apache-2.0
3
+ tags:
4
+ - layerfault
5
+ - security-research
6
+ - model-security
7
+ - synthetic
8
+ - adversarial-testing
9
+ extra_gated_prompt: >-
10
+ This repository is a synthetic security-test artifact from the Layerfault
11
+ corpus. It intentionally contains adversarial characteristics (e.g.
12
+ suspicious pickle opcodes, executable-format smuggling, prompt-injection
13
+ strings) designed to exercise security scanner detection rules. It is
14
+ **not** a usable ML model and must never be loaded or executed outside an
15
+ isolated scanner-testing environment. By accepting, you confirm you
16
+ understand this repository is a test fixture, not production model
17
+ weights.
18
+ extra_gated_button_content: I understand this is a security test fixture and accept the risk
19
+ gated: auto
20
+ ---
21
+
22
+ # hub-lfs-doc-pointer-control
23
+
24
+ > **SECURITY TEST ARTIFACT: DO NOT USE AS A PRODUCTION MODEL**
25
+
26
+ This repository is part of the Layerfault synthetic security corpus.
27
+ It is deliberately constructed to contain security-relevant characteristics for scanner testing.
28
+
29
+ **Corpus ID:** `LF-CH-HUBLFS-0010`
30
+
31
+ ## Purpose
32
+
33
+ Hub lfs doc pointer control.
34
+
35
+ ## Direct expected Layerfault rules
36
+
37
+ - None; this repository is a control/comparison input.
38
+
39
+ ## Candidate rules
40
+
41
+ These are deliberately plausible targets that remain marked as candidates until the exact
42
+ Layerfault build used for certification confirms them.
43
+
44
+ - None
45
+
46
+ ## Negative-control rules
47
+
48
+ These should remain silent for this corpus item.
49
+
50
+ - `LF-HUB-LFS-OID-INVALID`
51
+ - `LF-HUB-LFS-SIZE-MISMATCH`
52
+
53
+ ## Safety
54
+
55
+ The corpus uses fake secrets, loopback/`.invalid` network destinations, harmless marker output,
56
+ and synthetic model behavior only. It is intended for static scanning and isolated security testing.
57
+
58
+ ## Challenge classification
59
+
60
+ - Severity: **informational**
61
+ - Difficulty: **adversarial**
62
+ - Expected admission decision: **PASS**
63
+ - Control type: **negative**
64
+ - Attack surface: hub-lfs-state
65
+ - Techniques: lfs, doc, pointer, control
66
+ - Transformations: none
67
+
68
+ ### Ground-truth oracle IDs
69
+
70
+ - `LF-ORACLE-HUBLFS-0010`
71
+
72
+ These oracle IDs describe synthetic ground truth. They do not claim that a
73
+ matching Layerfault detector already exists. A challenge may intentionally expose
74
+ a scanner blind spot and remain unmapped until the detector is implemented.
SHA256SUMS.json ADDED
@@ -0,0 +1,22 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ [
2
+ {
3
+ "path": "CHALLENGE_ORACLE.json",
4
+ "sha256": "affa0ca2c78adac7cb5478ec561660e6829d1f08d0a15e3f13e958e8c0576315",
5
+ "size": 697
6
+ },
7
+ {
8
+ "path": "FIXTURE_LAYOUT.json",
9
+ "sha256": "00ffeeaec896e61fbe551abc1d84726a87df93dba63f8a537a107563ea92b1e0",
10
+ "size": 199
11
+ },
12
+ {
13
+ "path": "LAYERFAULT_CORPUS.json",
14
+ "sha256": "10805d28c0b8ac0ab7356e54407d55c2bb24f6ac7a9357e4f5627ff38a6ac442",
15
+ "size": 927
16
+ },
17
+ {
18
+ "path": "README.md",
19
+ "sha256": "463f362e316b788652f3eb72cd50eac916dd9e53c0b107970cb0ed6c3816c4f3",
20
+ "size": 2261
21
+ }
22
+ ]