[Security] Blind write access could cause problems

Abierto
  • ¿Algo no está bien?
#68 6 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
typescript
Área
backend, security

Línea de trabajo

Start by reproducing the issue's question: test whether transcluding a tiddler or using a sequence of widgets can cause a wiki change in the MultiWikiServer scenario. Trace whether a student-controlled bag can write or expose tiddlers from other bags; done when the attack is confirmed or ruled out and the affected access boundary is documented.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

@Jermolene @pmario

I've come across what I think may be a corner case, or may be something much more substantial. I'm not sure yet.

Consider the scenario where a teacher has a bag for each of his students which they can write to and he can read all their bags loaded in one recipe (maybe he enforces that they all name their tiddlers with some prefix, somehow, which is fairly easy to do with some minor UI tweaks).

Now each student has write access to one of the bags in the recipe, but cannot read most of them. However, a student may be able to come up with an attack which somehow allows them to modify their own bag in such a way that when the teacher loads his recipe, or clicks a button, or who knows what, it dumps all the tiddlers of all the students into that one student's bag.

Obviously the partitioned bags feature I keep talking about would enforce username prefixes at the server level to avoid trusting the user, and we can prevent bags from loading modules, so most of this can be mitigated quite well, but a few vectors may still be possible.

Question: Is there any sequence of widgets which would be able to cause a wiki change simply by transcluding a tiddler?

Lenguaje dominante
TypeScript
Estrellas
61
Forks
17
Merge medio
4 min
PR fusionados (30 d)
1

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TiddlyWiki/MultiWikiServer

Todos los issues de TiddlyWiki/MultiWikiServer

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.